Environment Parameter not being honored in MSBuild.exe


Badge +3


 

Symptoms


When deploy the package via MSBuild Command, the target environment parameter command not being honored after the upgrade.

Eg:-
Script command line : "C:WINDOWSMicrosoft.NETFrameworkv4.0.30319MSBuild.exe" [MSBUildName].msbuild /p:Environment=UAT

The target environment field is always taken from .msbuild property instead of command parameter.
 

Diagnoses


This is a known issue in Blackpearl 4.6.8

As a workaround, we are using the msbuild version of .Net Framework 3.5
 

Resolution

Logged as product issue to be fixed in future release.




 

0 replies

Be the first to reply!

Reply