StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In general, ALWAYS deploy Release builds to production. Debug will add to your assembly weight and degrade performance. </p> <p>If you are developing ASP.NET applications, leaving Debug mode on actually changes how/when your pages are compiled by the JIT compiler and significantly degrades performance to add better interactive debugging ability. </p> <p>As far as which build to deploy to development...if you are running unit tests against development, it is probably a good idea to deploy the Debug build so you can get the most debugging information when tests fail or exceptions occur. However, there is hopefully an additional Testing or Pre-Production environment where you can have your integration tests running and manual tests are performed there. That Testing/Pre-Prod environment should DEFINITELY be using Release builds so that you can see the true perfomance and compilation issues before going to Production. </p> <p>If you don't have this intermediate Testing/Pre-Prod level, then I would suggest running your Dev environment with Release. In other words, you should run at least one level before production in Release configuration. </p> <p>For more information on what you can do with configurations, I have a blog post specifically for Silverlight (<a href="http://blog.tonyheupel.com/2009/04/environment-specific-service-references.html" rel="nofollow noreferrer">http://blog.tonyheupel.com/2009/04/environment-specific-service-references.html</a>). In there is a link to Scott Hanselman's more generic article on build configurations and different environments.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload