How to exclude the Web.Config file while deploying

Automated deployment for web applications and databases

How to exclude the Web.Config file while deploying

Postby ganesh.mulimani » Wed May 07, 2014 9:24 am

Do we have solution to solve this problem.

I want to exclude my web.config file from the redgate package during my deployment step.

i dont want to deploy the web.config file to destination server.
ganesh.mulimani
 
Posts: 19
Joined: Fri Apr 25, 2014 12:12 pm

Postby Mike Upton » Thu May 08, 2014 8:41 am

To exclude the web.config from deployment, you'll need to stop it being put in the package in the first place. The web.config is an essential part of an IIS web application, so our default tools include it. You'll have to use RgPublish.exe with a .nuspec file if you want to customize the contents of the package.

However, you shouldn't need to exclude the web.config file at all. It's better not to rely on the existing contents of the application directory when doing a deployment. If you need the web.config to be different on the target server than it is in the source code, the best way to achieve that is using variable substitutions and/or config transformations.
Mike Upton

Project Manager - SQL Compare|Data Compare|Comparison SDK
Redgate Software Ltd.
Mike Upton
 
Posts: 190
Joined: Wed May 11, 2011 8:04 am
Location: Redgate


Return to Deployment Manager

Who is online

Users browsing this forum: No registered users and 0 guests