release-mode

today i found out that the compiled static library i'm working on is much larger in Release mode than in Debug . I found it very surprising, since most of the time the exact opposite happens (as far as i can tell). The size in debug mode is slightly over 3 MB (its a fairly large project), but in release it goes up to 6,5 MB. Can someone tell me what could be the reason for this? I'm using the usual Visual Studio (2008) settings for a static library project, changed almost nothing in the build configuration settings. In release, i'm using /O2 and "Favor size or speed" is set to "Neither". Could

I'm starting deployment of my web application and I need to guarantee that all the assemblies that are going to be deployed were built using Release configuration. Our system was developed using C#/.Net 3.5. Is there any way to achieve this? David Check this . The idea is that you get the list of assembly attributes using Assembly.GetCustomAttributes() and search for DebuggableAttribute and then find if such attribute has IsJITTrackingEnabled property set. public bool IsAssemblyDebugBuild(Assembly assembly) { return assembly.GetCustomAttributes(false).OfType<DebuggableAttribute>().Any(da => da

I have to debug a c++ project, but as one dependency doesn't compile in debug mode and I haven't been able to fix that issue so far, I'd like to try to debug the project in release mode. Currently the application crashes due to a null pointer, but I haven't the code that's causing the error. As break points apparently are ignored in release-mode, I'd like to know what's the best way find the error. Ed S. In VS, right click your project, chose "Properties". Click the C/C++ node. Set Debug Information Format to C7 compatible (/Z7) or Program Database (/Zi). Expand Linker and click the General

Is there any way to find out if an assembly has been compiled with the TRACE or DEBUG flag set without modifying the assembly? this. __curious_geek The only best way to do is check the compiled assemblies itself. There is this very useful tool called '.NET Assembly Information' found here by Rotem Bloom. After you install this it asociates .dll files to open with itself. After installing you can just double-click on the Assembly to open with it and it will give you the assembly details as displayed in the screenshop below. There you can identify if it's debug compiled or not. alt text http:/

I want to deploy the release version of my application done in C#. When I build using the Release config, I still can see that .pdb files are produced, meaning that my application can be still debugged. This also means that some debug information is present somewhere in my code, slowing it down a little bit. If this is true, how can I completely suppress any debug information produced in the binaries? Do you also know the reason of for having release .pdb ? The Release configuration has the Optimize code checked, and only the TRACE constant is defined, not DEBUG . Thank you for assisting. If