I'm trying to set up a deployment pipeline with msdeploy and so far I've hit a small "problem".
From the build environment to the production one there are several files which should not be copied, and I've found that I can do that by skip directives.
My main bother is that the directives can either be configured on a file that exists on the same directory as the msdeploy executable (not so good for build servers where different projects and configurations may wish to skip diferent files), or on the command line (which for more than 2 or 3 directives becomes a bit unwieldy).
I'd expect to be able to associate skip directives with a provider, but from what I managed to gather that is not possible. My expected syntax would be:
<sitemanifest>
<contentPath path="c:\source\website">
<skipDirectives>
<skipDirective name="ExcludeSvnDirectories">
<skip objectName="dirPath" keyAttribute=".\svn"/>
</skipDirective>
</skipDirectives>
</contentPath>
</sitemanifest>
Or perhaps being able to setup a .configfile local to the current working directory (and as such would be local to a given project).
Are there any workarounds for this problem?