Debug/Release Version. What's the diff?

[klone]

What's the difference between the debug version and release version of an application. I have a finished project which i've even created distribution packages - but I compiled a 'Debug version' so i'd like to know if there are any performance issues am unaware of or something. And if I need to compile a release version what am i required to do.

[Denaes]

What's the difference between the debug version and release version of an application. I have a finished project which i've even created distribution packages - but I compiled a 'Debug version' so i'd like to know if there are any performance issues am unaware of or something. And if I need to compile a release version what am i required to do.

I'm sure you could get away with using a "Debug" project.

 

 

Debug projects have more inline code for debugging information and I believe normally come with a seperate debugging file.

 

A Release version is a bit more streamlined and a little smaller.

 

If you want to switch the project type, it's normally up on the tool bar. If not, go to your solution explorer (the one that shows all the classes and forms), rightclick the solution and go down to properties or settings (I don't have VS.Net installed at the moment). I believe its in the build section or somewere around there.

 

Just remember that if you're not done, Release has awful debugging help if an error does come up, so remember to switch it back if you go back to debugging.

[samsmithnz]

The release version is supposed to be 'optimized' too, but I can't tell any difference...

[PlausiblyDamp]

Debug builds generally run slower as they are designed for debugging and relate to the source code and the .pdb files very closely.

In a release build all code that references the System.Diagnostics.Debug class are effectively removed and have no run time overheads. The compiler (and the JIT compiler) also may re-write parts of your code to a more optimal form (search google for specifics but they include standard compiler features like inlining, invariant hosting, moving constants out of loops etc).

For a finished project that is to be released to the public then use a release build - as Denaes said though debugging support is eriously hampered in a release build.

[Nerseus]

If you truly need some debugging in a Release build, you could always make use of the Trace class.

 

I'd go with Release for your final/public build.

 

-ner