All geek questions in one place

What is the difference between debug and release executables in .NET?

I am wondering what is the difference between debug and release binaries in .NET.

What happens when I put <compilation debug="true" /> instead of <compilation debug="false" /> in the web config file for any web service?

+4
source share
2 answers

This post can definitely answer your question.

When the debug = "false" / compilation is installed, the WebResource.axd handler will automatically set a long cache policy for resources received through this - so that the resource is loaded only once to the client and is cached there forever (it will also be cached on any intermediate proxy servers). If you have an Atlas application for your application, it will also automatically compress the content from the WebResources.axd handler for you when debug = "false" / compilation is set - reducing the size of any client javascript script library or static resource for you (and not requiring it’s up to you to write some custom code or configure something in IIS to get it).

+2
source

When you launch your web application in visual studio, you have two options 1. Launch in debug mode 2. Run without debug mode

If you set debug="true" , then it will create dlls (binaries) that will track debugging - Debug mode If you set debug="false" , then it will create dlls (binaries) that won't track debug points. - Release mode

-one
source

Source: https://habr.com/ru/post/1497399/

More articles:


All Articles