Upgrading from VS2005 to VS2008

I upgraded from VS2005 to VS2008 today.  The first server I publised to went off without a hitch.  I'm glad, because that gave me confidence that VS2008 was going to be a fairly easy upgrade.

Prior to upgrading, I did some research and found that .NET 3.5 is really the .NET 2.0 core with some added referenced assemblies.  Because of that, IIS still gives only the two options of ASP.NET 1.1 or 2.0.  Knowing that going in probably saved a lot of time because my next publish to another server revealed this issue:


 

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Child nodes not allowed.

Source Error:

Line 78: <compilers> Line 79: <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider,System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" warningLevel="4"> Line 80: <providerOption name="CompilerVersion" value="v3.5"/> Line 81: <providerOption name="WarnAsError" value="false"/></compiler></compilers></system.codedom> Line 82: <runtime>

Source File: C:\Inetpub\devads.sundropsystems.com\web.config    Line: 80


Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832  
 




Luckily, the solution to this problem was easily found.  It turns out that my 2nd server had 2 updates to .NET waiting in Windows Update.

KB110806 - .NET Framework 2.0 SP1
KB929300 - .NET Framework 3.0 SP1

These patches allow .NET to understand these child nodes: providerOption


 

What did you think of this article?




Trackbacks
  • No trackbacks exist for this post.
Comments
  • No comments exist for this post.
Leave a comment

Submitted comments are subject to moderation before being displayed.

 Name

 Email (will not be published)

 Website

Your comment is 0 characters limited to 3000 characters.