webdeploy

MsDeploy fails for webdeploy

*爱你&永不变心* 提交于 2019-12-07 01:40:32
问题 I am trying web-deploy. Because I wanted to be able to reproduce this, i used a test system Windows 2008 RC, IIs 7.5 + Deployment package I configured deployment using http://learn.iis.net/page.aspx/516/configure-the-web-deployment-handler/ Enabled tracing http://technet.microsoft.com/en-us/library/ff729439(v=ws.10).aspx I created a new WCF Service Application, (changed nothing) compiled it and tried to deploy I get the following response(after a few min) ------ Build started: Project:

Ignore file from delete during WebDeploy

若如初见. 提交于 2019-12-07 00:34:39
问题 I'm using TeamCity to build and deploy a collection of MVC Applications via msbuild and WebDeploy. In a step previous to my solution build/deploy, I copy an app_offline.htm to the deploy directory so that I can perform SQL updates and other web/solution management steps including the build. One of the setting in the WebDeploy is to delete files that aren't included in the project, or not needed to run the site. This deletes my app_offline.htm file each time. While I understand this is kind of

Why use Docker for .NET web apps when we have WebDeploy?

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-06 19:50:37
问题 In the Microsoft ecosystem, people were happily deploying web apps using WebDeploy Packages until Docker came along. Suddenly everyone started preferring to use Docker instead, with articles being written telling how to WebDeploy into a Docker image. I've searched this article (and others) for the word "why" and haven't found an explanation, leaving me to infer that the answer is just "because Docker." I'm probably oversimplifying, but it seems that WebDeploy Packages and Docker images serve

Web Deploy (aka MsDeploy) returns ERROR_CONNECTION_TERMINATED

夙愿已清 提交于 2019-12-06 18:51:45
问题 I am trying to execute from command line msdeploy like for example following command: "C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe" -verb:sync -source:package="Templates\TemplateAppPool.zip" -dest:appPoolConfig="MyAppPool",computerName="...",userName="...",password="..." -replace:objectName=processModel,targetAttributeName=idleTimeout,replace=00:45:00 -replace:objectName=add,targetAttributeName=managedPipelineMode,replace=Integrated -allowUntrusted And getting following error

Using WebDeploy (MSDeploy) to deploy to a Microsoft Azure Website target doesn't work

耗尽温柔 提交于 2019-12-06 15:28:36
I'm trying to deploy my web app via Visual Studio 2015's "Publish" functionality to an Azure website/app service staging slot and I receive the following errors: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4295,5): Warning : Retrying the sync because a socket error (10054) occurred. Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 1 of 10. Updating file (xxxxxxxxxxxxx__staging\bin\EntityFramework.dll). C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4295,5):

Web Deploy to Azure fails “Could not create SSL/TLS secure channel”

百般思念 提交于 2019-12-06 14:43:54
I always deployed from my local machine to Azure (Classic cloud service) but from yesterday I get this error: Could not complete the request to remote agent URL 'https://[MYNAME].cloudapp.net:8172/msdeploy.axd?site=Default Web Site'.The request was aborted: Could not create SSL/TLS secure channel The port is open. The web deploy is installed. As I see nothing has changed. I tried to install a new version of Web Deploy (3.6) but it didn't help. What else can be checked? Thank you. i faced the same problem: old 2008 r2 Server never changed anything cause (speculation): since visual studio 15.9

How can I pass MSDeploy-style parameters to MSBuild via the commandline?

你离开我真会死。 提交于 2019-12-06 08:20:25
问题 I am setting up TeamCity to deploy our Website Project application (using a *.wdproj) and Web Deploy application to IIS. I have a build configuration that uses MSBuild.exe with the MSDeployPublish to build and then deploy the application. We now want to get the application to deploy to multiple target environments, therefore need a way to supply different settings based on the target environment. I have added a parameters.xml file to the Web Deployment Project, and have verified that the

TFS 2012 Build Definition for web deployment ignores parameters defined in project files

怎甘沉沦 提交于 2019-12-06 07:40:59
问题 I'm trying to set up a TFS 2012 build definition that will build a solution and deploy several web apps within the solution. I came across this article that seems to address exactly what I'm trying to do and also seems to agree with the solution mentioned here. So I tried implementing the build definition/project configuration as described in that article, but no matter what I do, it seems to be ignoring the parameters I put in the specific configuration property group of the csproj files

How can resolve Untrusted certificates Error ?( TFS2013 Build and deploy to IIS )

一个人想着一个人 提交于 2019-12-06 06:00:43
I crate a build definition on tfs2013.when I queue my builddefinition I get an error about Untrusted certificates. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets (4270): Web deployment task failed. (Connected to the remote computer ("developertest") using the specified process ("Web Management Service"), but could not verify the server’s certificate. If you trust the server, connect again and allow untrusted certificates. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CERTIFICATE_VALIDATION_FAILED . I check help link and it

Create a clickonce webdeploy package

↘锁芯ラ 提交于 2019-12-06 01:12:57
问题 Is it possible to build a web deploy package containing a clickonce application that can be deployed to a web server using the standard webdeploy tool? Here would be the ideal process: MSBuild "YourFullyQualifiedProjectName.csproj/vbproj" /T:Package obj\Debug\Package\YourFullyQualifiedProjectName.deploy.cmd /Y The reasoning behind this would be so we can build the whole solution including web packages, run all tests, then deploy only after tests pass. I've currently looked at doing a file