Environment variables get lost between MSBuild projects

Posted by DotNetter on Stack Overflow See other posts from Stack Overflow or by DotNetter
Published on 2010-05-20T15:31:53Z Indexed on 2010/05/20 16:10 UTC
Read the original article Hit count: 419

Hi,

I have a .NET solution containing following projects:

  • web application (WAP)
  • web deployment (WDP, .wdproj)
  • wix setup (WIX, .wixproj)

In the WDP I've used a custom MSBuild task (SetEnvVar) to set some env. variables for further use in the build process. After setting them I can use them without prob. in the WDP but in the WIX they are empty/undefined. The strange thing is that when I reference those env. vars in the WIX files (by using properties in .wxs or preproc vars in .wxi) I get the values as expected.

Do you have any idea why the env. vars get lost/are undefined in .wixproj?

By the way the (solution) build process is triggered from inside VS 2010.

© Stack Overflow or respective owner

Related posts about .NET

Related posts about msbuild