Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
tools
vsnet.act
vsnet.debugging
vsnet.documentation
vsnet.enterprise.tools
vsnet.general
vsnet.ide
vsnet.jlca
vsnet.servicepacks
vsnet.setup
vsnet.vsip
vsnet.vss
vsnet.vstools.office
vstudio.development
vstudio.extensibility
vstudio.general
vstudio.helpauthoring
vstudio.setup
vstudio.sourcesafe
  
 
date: Mon, 14 Jul 2008 12:07:00 -0700,    group: microsoft.public.vsnet.general        back       


Compiling for Production: Release vs. Debug   
We have developed a number of different applications (ASP.NET web site, 
Windows services, DLLs, Windows forms, etc.) in C# 2.0.  We have developed 
and unit tested all these applications/components using Debug mode.  Now we 
are ready to compile everything for release to production.  However, we don’t 
know whether we should compile all the applications/components/assemblies 
using Release mode (or keep everything in Debug mode).

We’ve tried researching Debug mode vs. Release mode but have been unable to 
find any concrete information on which one is better, which one should be 
used in production and why, if Debug in production is good or bad, etc.

So, we’re posting the question(s) here:

- Should we compile in Release mode for a production release and why?
- Are there any issues releasing Debug mode applications/assemblies into 
production?
- What (if any) are the main differences between Release and Debug modes?

Thanks.
date: Mon, 14 Jul 2008 12:07:00 -0700   author:   lmttag

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us