Due to the simplicity of the XCOPY deployment strategy in ASP.NET you can easily set your self up for dumb mistakes. It took me a good 15 minutes (a little embarrassing) to realize what my deployment issue was below.

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: Unrecognized attribute 'xmlns'.
Source Error:

Line 1:  <?xml version="1.0"?>
Line 2:  <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
Line 3:  	<system.web>
Line 4:  		<compilation debug="true">

Source File: C:\Inetpub\wwwroot\TTCOG\web.config    Line: 2


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

It screamed at me in the red line (and the version information) but I could not quite see it ... then I realized when you manually create a virtual directory for your project it defaults to version 1.1. This was my first official 2.0 deploy so I can be excused for this oversight.

image

"Nothing ever comes to one, that is worth having, except as a result of hard work." - Booker T. Washington

Technorati tags: , ,