webdeploy

问题 I am struggling with the massive beast that seems to be WMSvc - Web Management service for IIS. I am trying to deploy web sites from Visual Studio which is killing me. Actually it's killing everyone except me on my team, but since I am designated web server manager right now I'm the one thats feeling the hurt. It works when I deploy using my Admin windows account, which atleast means I should be on my way, but it doesn't work with another account that isn't admin or an IIS manager account.

问题 I've read many posts, documentation pages etc. regarding WebDeploy via VS2012 and via command line. In all of the deployment scenarios, I noticed that the destination site should already exist on the destination machine (IIS). Is there an option to create a package that creates the site if it doesn't exist on the destination (hosting) machine? 回答1: The appHostConfig provider will create a site on the remote server. It comes with a million caveats on setting the remote bindings and physical

问题 I have and .net/angular2 application, I'm publishing with WebDeploy. But when the publish finish I wanna run some command on the target machine like npm install npm run tsc There is a way to do that? 回答1: You should be able to use the postSync argument: msdeploy -verb:sync -source:contentPath="C:\Test1" -dest:contentPath="C:\Test2" -postSync:runcommand="c:\MyBatchFile.bat" https://technet.microsoft.com/en-us/library/dd569089(v=ws.10).aspx 来源： https://stackoverflow.com/questions/39454497/net

问题 I'm trying to configure a runCommand to wait more than the default value of 1 second to finish. This is a sample pubxml code: <ItemGroup> <MsDeploySourceManifest Include="runCommand"> <waitInterval>60000</waitInterval> <path>"C:\Company\install-services.cmd"</path> </MsDeploySourceManifest> </ItemGroup> When I start a deployment, it successfully creates a *.SourceManifest.xml file in the temp package directory, but it only includes the path: <runCommand path=""C:\Company\install-services.cmd"

问题 Goal is to deploy Azure App Service with WebDeploy package from VS2015 with all web.config transformations applied according to current solution build configuration. I have tried adding build configuration to ARM deployment project and it works fine when you build it from Visual Studio. WebDeploy package for web project is created with correct web.config transformation applied. However if you use Deploy dialog referenced web project is always built and packaged with default build

问题 Using Team Foundation Server continuous deployment with Web Depoly, is it possible to stop certain folders being deployed? And if it is, how? UPDATE You can't specify a skip rule via the command line (as in, an MSBuild Argument) because they are declared as items, not properties. A skip command can be specified in a publish profile. However it seems publish profiles are only for the inbuilt publishing in visual studio, not Web Deploy 3. Is there a way for Web Deploy to accept a publish

问题 I’ve been testing the new web deploy tool with VS 2012 but I have this issue: I get this extra connection string added to my published web config that I don't currently have in my projects web config. <add name="name" connectionString="name_ConnectionString" providerName="System.Data.SqlClient" /> Where could this be coming from? It seems like is a relic from past conn strings I've used.. Hope this explains my issue :0) Thanks for any assistance Quantum 回答1: It has to be coming from one of

问题 I am setting up a new dev server, and moving some old projects to this. I opened up one of the older web projects. Setup the publish settings to use Web Deploy just like I have done for many projects. However, on this one I am getting the following error when clicking the preview. Error 3 The "NormalizeServiceUrl" task was not given a value for the required parameter "ServiceUrl". If I try to publish with out preview, I get an additional error. Web Deploy publish/package validating error:

问题 On the destination server I want do delete a folder (and all it's files) under the App_Data folder. It should happen just before I push the new files to the destination server. How can I to this? Current configuration <PropertyGroup> <WebPublishMethod>MSDeploy</WebPublishMethod> <LastUsedBuildConfiguration>QA</LastUsedBuildConfiguration> <LastUsedPlatform>Any CPU</LastUsedPlatform> <SiteUrlToLaunchAfterPublish>http://qa.mysite.test:80/</SiteUrlToLaunchAfterPublish> <LaunchSiteAfterPublish

问题 I have a solution that contains a bunch of class library projects and an IIS website. I am trying to configure teamcity to compile and deploy the website project via MSBuild/web deploy. The projects all build fine but it seems that it is ignoring the command line parameters to push the site to the specified server my question is, is it possible to achieve what I am looking to do? or can this only be done with a web application project? /P:Configuration=Release /P:DeployOnBuild=True /P