I've got an ASP.NET application that I develop on my local machine and deploy to a Win Server 2003 server after testing. The Web application runs just fine on the Web server, so there's not really a problem except...I got configuration errors the first time I deployed the site to the server because of all of the Microsoft.VisualBasic.xxx references added to the compilation/assemblies section of web.config. So...I removed them all and redeployed to the server. Voila! A working site!
Now, whenever I rebuild the project, Visual Studio attempts to check web.config out of VSS and modify it. This breaks my deployment so I have to keep removing the references. Is there a reason for this? I'm attaching the compilation section of my web.config without all of the useless references:
<compilation debug="true" defaultLanguage="vb" explicit="true" strict="false">
<assemblies>
<add assembly="System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Runtime.Serialization.Formatters.Soap, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</assemblies>
</compilation>
Could it be because I have debug set to true (which I always need to remember to change before deployment)?