Overriding parameter values VIa a MSBUILD Item Group So I decided to dig deeper and find a solution. ![]() I still think this is a better approach which provide more capabilities but I’ve seen this question too many times now. In the past I have suggested to just use MSDeploy.exe to deploy. It seems to me that they were in the process of adding setParam and setParamFile support in MSBuild, but then abandoned it. The targets file contains some unused code that hints at better support for MSDeploy parameters (in ). Although there are hints of this functionality as Steven pointed out in the most recent StackOverflow post: They also usually have multiple environments beyond just their local configuration.Įach time I see this question I go back and re-review the web publishing targets file which is located at (adjust for your version of VS):Ĭ:Program Files (x86).targetsĪnd each time I come to the same conclusion, the MSDeployPublish target does not support overriding the parameters. The typical scenario is the developer wants to deploy the web application with a environment-specific set of parameterization values. These targets are used when publishing via Visual Studio or can be triggered by setting the MSBuild properties DeployOnBuildequal to “true” and DeployOnTargetto “MSDeployPublish”. ![]() Over the last few months I’ve seen several questions regarding setting WebDeploy parameterization values when deploying via MSBuild using the MSDeployPublish and related targets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |