Friday, October 2, 2009

Old Include files are a pain

Noticed an issue with migrating old ASP application to our new CruiseControl deployment model today.  That is, using of ASP include files *.inc in your project causes Visual Studio to not deploy these to the “Published” sites as it does not understand the file extension. 

image    

In the example above you can see that the Build Action is “None”.

To get around this you need to manually set the Build Action property to “Content” in Visual Studio.

image

From that point on the file will be automatically included with the deployment of the site.  This will not affect any of the new ASP.NET solutions, only the very old ASP solutions.