msdeploy

问题 I need to do this but one step leads me to uncheck the "Allow this precompiled site to be updatable" option, but I don't see that in the publish website dialog on Visual Studio 2010. Does anyone know how can I do that on Visual Studio 2010? 回答1: This option is available for ASP.Net Web Site projects not ASP.Net Web Applications . Right click on the solution explorer and select Add New Web Site...against that you will get that checkbox Check out this Web Application Projects versus Web Site

问题 Our product is an ASP.Net web application. Currently, we use Web Site Projects in Visual Studio, but have been looking into using Web Application Projects for quite some time. I am currently researching them so that we can hopefully improve our deployment process. We have a base web site that is shared and common between different clients, and then we extend that with client-specific functionality in client Web Site Projects. The client projects extend base, and therefore rely on its contents

问题 I have found out how to set the application pool and default value <parameter name="applicationPool" defaultValue="MyDefaultValue" > <parameterEntry kind="DeploymentObjectAttribute" scope="application" match="application/@applicationPool" /> </parameter> Does anyone know how to set the "IIS Web Application Name"? It gets generated in the SetParameters.xml file as <setParameter name="IIS Web Application Name" value="Default Web Site/MySite_deploy" /> I can overwrite the SetParameters.xml file,

问题 I have found out how to set the application pool and default value <parameter name="applicationPool" defaultValue="MyDefaultValue" > <parameterEntry kind="DeploymentObjectAttribute" scope="application" match="application/@applicationPool" /> </parameter> Does anyone know how to set the "IIS Web Application Name"? It gets generated in the SetParameters.xml file as <setParameter name="IIS Web Application Name" value="Default Web Site/MySite_deploy" /> I can overwrite the SetParameters.xml file,

问题 I am trying to have my web application automatically Publish when a Release build is performed. I'm doing this using the _CopyWebApplication target. I added the following to my .csproj file: <!-- Automatically Publish in Release build. --> <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" /> <Target Name="AfterBuild"> <RemoveDir Directories="$(ProjectDir)..\Output\MyWeb" ContinueOnError="true" /> <MSBuild Projects="MyWeb

问题 I am creating Web Deployment Package zip files for my Web Applications I found I am able to specify the Site Name of the application by including a pubxml during the packaging of my site and using the PublishProfile property during the build to specify that profile. The pubxml has <DeployIisAppPath>WebSiteName</DeployIisAppPath> in it and that creates the site name as seen in the IIS Management screen. I'd like to specify the location on disk of the website when it is deployed to a server

问题 In my Visual Studio 2010 SP1Rel, MS web deploy has suddenly stopped workingwith this error: Unrecognized argument 'Web'. All arguments must begin with "-". The argument "Web" refers to the parameter "Default Web Site", ie web deploy cannot deploy if the path contains spaces. This worked until today. If I rename my website to DefaultWebSite (no spaces) then the error message changes to: Unrecognized argument 'Source=10.10.10.1\MSSQLSERVER,1432;Initial'. All arguments must begin with "-". There

问题 We practice continuous deployment with TFS (2008) and are looking for a nice way to handle IIS settings changes. MSDeploy seems like it should be the way to handle this, but after much reading and searching, I haven't found a good answer. The problem with MSDeploy, as I see it, is that you need to create a deployment package using an existing IIS website. I would like to be able to have the appropriate IIS configuration for the website in source control and have the build create the package.

问题 We practice continuous deployment with TFS (2008) and are looking for a nice way to handle IIS settings changes. MSDeploy seems like it should be the way to handle this, but after much reading and searching, I haven't found a good answer. The problem with MSDeploy, as I see it, is that you need to create a deployment package using an existing IIS website. I would like to be able to have the appropriate IIS configuration for the website in source control and have the build create the package.

问题 We are trying to integrate a 'build once, deploy anywhere' model in our build-deploy system. MSDeploy works wonders for this, cutting down build time dramatically with CRC checksum comparisons and ( for the most part ) it works just as well when using parameterisation to change applications web.configs depending on the environment we deploy to. I have the majority of these parameters nailed down, but a few elements and attributes never seem to change, no matter how many different ways I call