1

Closed

Version 2.1.0.0 - debug vs release mode & 'debug info' setting

description

The .NET assemblies are C# compiled with VS2010 SP1 using .NET 4.
 
It doesn't seem to report the debug/release, optimized/not otimized, and edit & continue correctly in some cases based on the following. The debug/release seems to be tied to the 'debug info' setting - not the config setting.
 
For my first test, I had the configuration set to 'release' and the optimze code was checked for all 3. The only setting I altered was the 'debug info' setting.
1.) debug info=full: debug, optimized, MSIL seq., edit & continue disabled.
2.) debug info = none: release, optimized, pdb seq., edit & continue disabled
3.) debug info = pdb-only: release, optimized, MSIL seq., edit & continue disabled
 
Then I set the configuration to 'debug' and the optimize code was unchecked for all three.
1.) debug info = full: debug, not optimized, MSIL seq., edit & continue enabled
2.) debug info=none: release, optimized, pdb seq., edit & continue disabled.
3.) debug info = pdb-only: release, not optimized, MSIL seq., edit & continue disabled
Closed Mar 30, 2012 at 6:25 PM by hi_its_ashu

comments

hi_its_ashu wrote Mar 30, 2012 at 6:25 PM

Hi Jeffrey,
What you see using the application is perfectly correct. To understand this you need to understand that Release and Debug are configurations that provide some default things. Just picture it as 2 different configuration without it's meaning.

So, if you change what goes into these configurations (debug info or optimization) then you are completely changing what debug/Release had to provide by default.

Eg: A debug build (with default config) means that it will have lot's of debugging information and no optimization. So, now in a Debug configuration, you change these 2 parameters, it's equivalent to a Release build.

Regards,
Ashutosh

wrote Mar 30, 2012 at 6:25 PM

wrote Feb 14, 2013 at 6:58 PM

wrote May 16, 2013 at 9:05 AM