This post originated from an RSS feed registered with .NET Buzz
by Scott Hanselman.
Original Post: Should one go to Production with a DEBUG Build?
Feed Title: Scott Hanselman's ComputerZen.com
Feed URL: http://radio-weblogs.com/0106747/rss.xml
Feed Description: Scott Hanselman's ComputerZen.com is a .NET/WebServices/XML Weblog. I offer details of obscurities (internals of ASP.NET, WebServices, XML, etc) and best practices from real world scenarios.
Here's a question that I'd really like to stir up some talk/comments/feedback.
Should one go live with a .NET (in this case ASP.NET) app compiled as DEBUG?
Some folks have claimed that whatever speed you might gain is pale compared to the
usefulness of the occasional late night production debugging session. A RELEASE
build strips out Debug.Write calls, etc., but we use Log4net exclusively, so that
doesn't affect us.
Thoughts and comments, oh wise bloggers? Is this clever, controversial, or stupid?