Debug vs. Release

  • Thread starter Thread starter Keith
  • Start date Start date
K

Keith

I understand that Debug should be - troubleshooting one's
code, etc. - and release should be when one has
the "final" version of one's code for release.

But what is the difference in VB/VS.NET?
Both version create a complied version - but in different
folders. That can't be the only difference.
Are Release apps any faster than Debug apps?
Are there any other differences?
Is it "ok" to use Debug applications for "actual" end-user
use?

thank you.
 
Keith said:
I understand that Debug should be - troubleshooting one's
code, etc. - and release should be when one has
the "final" version of one's code for release.

But what is the difference in VB/VS.NET?
Both version create a complied version - but in different
folders. That can't be the only difference.
Are Release apps any faster than Debug apps?
Are there any other differences?
Is it "ok" to use Debug applications for "actual" end-user
use?
Click to expand...

Release will have a few more optimisations enabled, and Debug generates
a .pdb file as well, which the CLR notices and uses. If a .pdb file is
present, it runs the CLR in a less optimised way (no inlining, less
aggressive garbage collection etc, I believe).
 
Debug and Release settings control what happens when you build your
application. You should use the Release setting when you're building
for production and will not need to debug the application. When you
build the application in Release mode, the debug symbols are not baked
into the assembly, so you cannot debug it using Visual Studio .NET or
other source code debuggers. The code is also optimized during this
build operation. And, all calls to Debug class methods in your code
are disabled while calls to Trace class methods are left.
when you compile in Debug mode, the application can be debugged at the
source level and you have all the power of Visual Studio .NET and
other source-level debug tools at your disposal (read on for more
information). Obviously, code compiled in Debug mode does not perform
quite as well as Release-mode code does.

Thanks

Anamika
 
Debug and Release settings to control what happens when you build your
application. You should use the Release setting when you're building
for production and will not need to debug the application. When you
build the application in Release mode, the debug symbols are not baked
into the assembly, so you cannot debug it using Visual Studio .NET or
other source code debuggers. The code is also optimized during this
build operation. And, all calls to Debug class methods in your code
are disabled while calls to Trace class methods are left.
When you compile in Debug mode, the application can be debugged at the
source level and you have all the power of Visual Studio .NET and
other source-level debug tools. Obviously, code compiled in Debug mode
does not perform quite as well as Release-mode code does.

Thanks

Anamika
 
Back
Top