-
Posted to
Web Deployment Tool (MS Deploy)
by
moshaikh
on
14 hours, 40 minutes ago
Yes with a negative lookahead regex as: [What it means is it will skip everything thats not asp, so essentially you copy only the asp files]
msdeploy -verb:sync -source:dirPath=c:\inetpub\wwwroot -dest:auto
-skip:objectName=filePath,absolutePath=\.(?!asp)
-
Posted to
Web Deployment Tool (MS Deploy)
by
moshaikh
on
11-23-2009, 9:33 PM
It will not be able to overwrite any file that is in use. But you can use presync and postsync to stop and start iis (or stop and start apppool). This way the gacAssemblies will get replaced by one command.
msdeploy -verb:sync -source:gacAssembly=Myassembly.assembly -dest:auto,computername=server -presync:runCommand="c:\stopiis.cmd" ...
-
Posted to
Web Deployment Tool (MS Deploy)
by
moshaikh
on
11-23-2009, 2:31 PM
1) TO exclude the web.config file only from the root directory. If you have the root directory named mydir then
msdeploy -verb:sync -source:dirPath=e:\sourcedir\mydir -dest:dirPath=e:\dest -skip:objectName=filePath,absolutePath=mydir\\web\.config
2) Why do you want to skip a web.config from n levels. For this you can write a custom rule that ...
-
Posted to
Web Deployment Tool (MS Deploy)
by
moshaikh
on
11-19-2009, 4:04 PM
I think the real issue is that you need to use processor architecture.
Add the ( processorArchitecture=<x86/amd64/msil > ) or use the shortname gacAssembly path="System.Web”
Let us know if this does not work for you.
-
Posted to
Web Deployment Tool (MS Deploy)
by
moshaikh
on
11-19-2009, 12:33 PM
can you make two changes and try and let me know how it goes:
Change the manifest as:
<MSDeploy.gacAssembly>
<gacAssembly path="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</MSDeploy.gacAssembly>
and run the command with the debug switch as:
"C:\Program ...
-
Posted to
Web Deployment Tool (MS Deploy)
by
moshaikh
on
11-19-2009, 9:06 AM
You can have as many skip rules and skip directives you want. There is no restriction in this regard.
Let us know if you need help figuring out the skip rules syntax
-
Posted to
Web Deployment Tool (MS Deploy)
by
moshaikh
on
11-16-2009, 5:26 PM
Yes you can use msdeploy to sync all website configuration. While doing this you can skip rules to skip what you dont want or use replace rules or setparam to change what gets synced.
For e.g.
msdeploy -verb:sync -source:webserver60 -dest:auto,servername=myserver -disableLink:Content
This syncs everything except for the content as that has been ...
-
Posted to
Web Deployment Tool (MS Deploy)
by
moshaikh
on
11-12-2009, 5:22 PM
Yes you can run the tool again with the includeACLS switch but it will undo any changes that you might have done to your destination after the earlier sync.
I would suggest syncing just the content folder in question with the includeACLS switch as this is the minimum risk and also run with whatif for the first time to see what its doing ...
-
Posted to
Web Deployment Tool (MS Deploy)
by
moshaikh
on
11-12-2009, 5:16 PM
msdeploy -verb:sync -source:apphostconfig -dest:auto -disableLink:Content
This should sync just the application host config settings from the source to the destination with no content.
Let us know if you need more information.
-
Posted to
Web Deployment Tool (MS Deploy)
by
moshaikh
on
11-11-2009, 2:21 PM
This might be an issue with ACLS of the folders that the files reside in.
By default we dont carry over the ACLS for you when you do a sync. But you can ask for the ACLS to be carried over as:
msdeploy -verb:sync -source:webserver60,includeALCS=true -dest:auto,computername=name -verbose
The includeACLS switch instructs that the ACLS of the ...