makefile - Why can I use some environment variables in some of the elements in the csproj file but not others in msbuild? -


What are the reasons for the following strange behavior, and how do I track issues?

We use a combination of files and a combination of msbild.

I have a project that has a strong name. I used to first use this kind of project file in S.N.K. Was founded by:

  & lt; AssemblyOnGreenTareIfile & gt; $ (Environmental) TheKeyName.snk & lt; / AssemblyOngeneratorfile & gt;  

The environment variable was defined in the batch file, which launched the shell for such a build:

  set environmentally = 'sappath'  

And it worked fine. Now I need a string name to be able to change, so it can be different on dev machine and release build server. There is a variable that exists to hold the full name key file to catch the full path, which is called a string named Strongam, it is defined in the msbuild environment, and if I put some text output into the target or property files, that the msbild function As part of that which builds the project, I can see that this Strongmanmefile indicates the correct place. So I changed csproj to change it:

   

But when I try and compile it, it is evaluating to clear and no / keyfile is not specified during the build.

We also define variables in files that can be accessed in csproj as well, they are used to indicate the place of referenced DLL, so that they differ on dev and build machine May be. I know that they have been set because these references come out correctly and everything is compiled, but if I try to use one of these variables in the AssemblyGirner's file element, then to empty it in that element Evaluates, but works in the reference element.

Why can this happen? AssemblyOriginatorKeyFile is specially treated in some way? How can I go about tracking the reasons behind this?

There is no good reason why this should be - as you know it simply works ; This is likely to be something in the series leaving it on the floor.

One thing to try is clearly passing through / p: StrongNameKeyFile = XX - which will end the right publicity by examining the environment and your inquiry.

Another potential thing is that using some names vy something else is clobbering the variable as?

Run with / v: diag and you'll get all the inputs and / or the changes they make as they change the dumps.

Or if on V4, use

and buy


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -