Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Referencing MSBuildExtensionPath property in another property does not allow fallback #1735
Consider the following msbuild file:
<Project> <Import Project="$(MSBuildExtensionsPath)\foo" /> </Project>
When you attempt to build this project, you get the following error:
Which clearly states that it attempted to import the project and attempted to fallback to the
Now consider this slightly modified project file:
<Project> <PropertyGroup> <MyExtensionPath>$(MSBuildExtensionsPath)</MyExtensionPath> </PropertyGroup> <Import Project="$(MyExtensionPath)\foo" /> </Project>
When this project is ran, the value of
As you can see, in this case msbuild only attempted to import from the local DevEnv path and no fallback was attempted.
Unsure. In the ideal case, when processing
I suspect that this might be difficult, perhaps the error message could be expanded to reference the case that one might be using
At minimum, this should be documented in case a user trips over it.
The current source for the Evaluator explicitly references this situation as unsupported:
referenced this issue
Mar 16, 2017
@drolevar FYI PreEmptive/Dotfuscator will be releasing an updated version in the next few days that works around this issue. In the meantime we've posted a Knowledge Base article that gives a few options for working around it manually - see Issue: Building a VSIP project in Visual Studio 2017 fails since it cannot find PreEmptive.Dotfuscator.Targets.