2

I have a solution with multiple projects, from which one is a web application of that I want to create deployment package. When publishing with Visual Studio, it publishes and deploys without any problems.
Due to some requirements, however, I need to publish it with command line and this is where I am having problems. Publishing alone works fine even in command line, but when I try to deploy package created in command line I get this error:

A value for the 'setAclUser' setting must be specified when the 'setAcl' provider is used with a physical path.

My msbuild command looks like this:

msbuild Solution.sln /p:DeployOnBuild=true /p:PublishProfile=Debug

One differences I noticed are that when publishing solution, PackageTemp folder is created in different projects and so when deploying it is printing different paths to cmd. With VS publish they look something like

"Default Web Site/MySite/..."

but with command line publish they look like this

"C:\MySolution\Project(only a library project, not the one I want to publish)\obj\Debug\Package\PackageTemp..."

Thanks for any help

Edit: Created .zip packages are almost the same, except for archive.xml which has some different values and I suspect this to be the problem, but unfortunately I can't make any sense of what does this file actually represent.

Ivan
  • 65
  • 6
  • Check this related answer on SO - http://stackoverflow.com/questions/6861990/can-web-deploys-setacl-provider-be-used-on-a-sub-directory – Mitul Oct 20 '15 at 17:42
  • I've seen that post and thought it does not relate to my problem. Now that you posted it I've tried it and it worked... but just for a while. I have no idea why but some times it works and some times doesn't. I came closer to identifying the problem, tho. Actual problem is that destination of package is set to C:\MySol\MyProj\Package\PackageTemp..., while it should be Default Web Site/.... I have no idea why, I set it in Debug.pubxml to Default Web Site/WebSite. Any ideas? – Ivan Oct 21 '15 at 14:55
  • Ok, after some more experimentation, it seems that whenever is set as full path, deployment fails, but whenever it is set just as relative path it works fine. I don't know how relates to the actual deployment destination, I thought it only server as a destination to save the package. Any explanations ? – Ivan Oct 22 '15 at 08:51

0 Answers0