Nick
Sat Jun 04 13:52:41 CDT 2005
Wow... you really hit a lot of forums. I'm assuming that you are facing a
serious challenge.
The most common cause I've seen for this is because you do not have all of
your compilation happening in a single solution file, and your references
are pointing to fixed locations on the hard drive.
In other words, I have seen this in the following scenario. If this
scenario does not apply to you, then my message will not be useful.
a) your application has more than one assembly.
b) you have not included the compilation of both assemblies in a single
solution file. You are compiling multiple solutions
c) The references in the dependent application are referring to the
location of the compiled dlls. They are not project references.
In this case, I have seen folks create two project files: one for debug and
the other for release modes, since the debug and release dlls for the
dependent app are in different directories. This is error prone and often
fails.
The best answer is to create an altogether new solution file. Add in all of
your project files. Drop all of the references and recreate them as project
references. Now, compiling as debug or release will work far better.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Ariel" <ariellarraburu@yahoo.com.ar> wrote in message
news:%23%235sYxEaFHA.228@TK2MSFTNGP12.phx.gbl...
>I have an application that works correctly in debug mode but it does not
>work in release.
>
> I am not using anything of the class system.diagnostics.
> I tried to disable the optimization code, but this did not work
>
> please I need a solution quickly!!.
>
> Thanks.