The miriad of different web.config settings have always been a bit of a mystery to me. I'm glad Microsoft has cleaned up some of the content put there by default, but it's still causing problems.
Specifically, Visual Studio 2015 is placing the following section in the generated web.config of a standard ASP.NET MVC application.
<compiler language="c#;cs;csharp" extension=".cs"
type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
warningLevel="4" compilerOptions="/langversion:6 /nowarn:1659;1699;1701"/>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb"
type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
warningLevel="4" compilerOptions="/langversion:14 /nowarn:41008 /define:_MYTYPE=\"Web\" /optionInfer+"/>
This program is blocked by group policy. For more information, contact your system administrator.
Since ASP.NET 2 is it possible to upload your site to your hosting without compiling it. Then the site will be compiled on the initial request using the compiler settings as seen in the web.config. If you pre-compile your site but still have code in the
App_code folder those settings will be used to compile that code.
I think that go-daddy disabled compiling on their servers so no malicious code can somehow be inserted and compiled/executed.
As long as you don't use the
App_code folder and you pre-compile your website you can delete the
web.config section you mentioned.
For more information about the
App_code folder check:
For more information about dynamic compilation of ASP.NET check: