Setting <compilation debug="true/false">
in Web.config seems to do things that you can also set in Visual Studio in Project properties, Build tab. Are they connected somehow? Does one of them takes precedence when compiling?
相关问题
- How to know full paths to DLL's from .csproj f
- Importing NuGet references through a local project
- Visual Studio 2019 - error MSB8020: The build tool
- 'System.Threading.ThreadAbortException' in
- VS2017 RC - The following error occurred when tryi
相关文章
- How to show location of errors, references to memb
- How to track MongoDB requests from a console appli
- Visual Studio Hangs on Loading UI Library
- How to use Mercurial from Visual Studio 2010?
- Build errors of missing packages in Visual Studio
- Copy different file to output directory for releas
- Edit & Continue doesn't work
- “Csc.exe” exited with code -1073741819
Set compilation debug="true" to insert debugging symbols into the compiled page. Because this affects performance, set this value to true only during development.
They are not connected. The compilation tag is ASP.NET only, while the project option one is for Windows Forms, console, WPF and so on.
ASP.NET compilation is so special, so you have to dive further to learn about every piece of it,
http://msdn.microsoft.com/en-us/library/ms178466.aspx