What will impact if i set RedGateNotAWebSite=True

ganesh.mulimaniganesh.mulimani Posts: 28
edited May 8, 2014 4:09AM in Deployment Manager
We are already using our website and all the IIS settings are done.
Now we are using RedGate Deployment Manager Tool.
Just i want to deploy or update the package to our existing project location and i don't want to set the IIS settings for it because its already done.


I am using the below property to do that. Please suggest me if i am wrong or missing something.

Variable Name: RedGateNotAWebSite
Value: True
Environment: Development
Traget: Dev
Step: All

Variable Name: RedGatePurgePackageDirectoryBeforeCopy
Value: False
Environment: Development
Traget: Dev
Step: All

Variable Name: RedGatePackageDirectoryPath
Value: [Application Physical Location]
Environment: Development
Traget: Dev
Step: All

Comments

  • Setting RedGateNotAWebSite to true will skip the IIS configuration stage of the deployment. Those variable settings look fine, although you can just leave the Environment and Target scopes at 'All' unless you want the deployment to behave differently for other environments or targets.

    Is something not working as you expect?
    Development Lead
    Redgate Software
  • Hi Mike,

    Everything is working as i expected and i followed your instruction for Environment and Target.

    But when i deploy the package it will deploy the web.config file as well.
    In our case web.config file differs from one environment to another.

    I am looking for the option to exclude the web.config file during my deployment.
    Currently i am copying the old web.config file manually after my deployment.

    Please help me to solve this issue.
  • I'm glad the variables are working as expected. I've replied to your other forum post about excluding the web.config file here.
    Development Lead
    Redgate Software
Sign In or Register to comment.