Location of $(MSBuildExtensionsPath32)

Question

Hello,

Is there anyway I can see where $(MSBuildExtensionsPath32) points to?

I tried echo $(MSBuildExtensionsPath32), echo $MSBuildExtensionsPath32, echo %MSBuildExtensionsPath32%, but it doesn't act like a environment variable like, for instance echo %windir% would.

I also tried searching through the registry, to no avail.

 Thanks,

Eric

Answer 1

Hi,

Please consult your question to MSBuild forum. http://social.msdn.microsoft.com/Forums/en/msbuild/threads/

Best Regards,

Larcolais

---

Larcolais Gong[MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 2

Hi Eric,

I just had the same question and found the anwser. It's usually this directory: C:\Program Files (x86)\MSBuild (on Windows 64 Bit)

or C:\Program Files\MSBuild (on Windows 32 Bit)

Further details: http://msdn.microsoft.com/en-us/library/ms164309.aspx

Ralf

Answer 3

Hi MSDN support. It's very very stupid to ask OP to resend a new request in a different place. It's not your job make issues goto the close state, OK? You should make the issue really closed, I mean really fixed. The MSDN forum is publicly to everyone, not your Corporation private forum. You guys don't have a correct service attitude.

Answer 4

You can set a new enviroment variable for MSBuildExtensionsPath32 and it will really works. The fact is:

If the envvar MSBuildExtensionsPath32 exists, the specified value will be used; Else will use the MSBuild installation folder as its default value.

Answer 5

Appropriate thing to do would have been to answer the question, and then direct to the other forum for next time.

Answer 6

@Larcolais terrible response.  if you linked to a specific thread that answered the question i would understand, but you're basically asking us to dig through an entire forum.

Answer 7

Hi MSDN support. It's very very stupid to ask OP to resend a new request in a different place. It's not your job make issues goto the close state, OK? You should make the issue really closed, I mean really fixed. The MSDN forum is publicly to everyone, not your Corporation private forum. You guys don't have a correct service attitude.

I 100% agree with this statement. This sort of thing is all over the MSDN forums and is why everybody goes to stack overflow instead.

Answer 8

Need to set MSBuildExtensionsPath32 system variable to C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild
Bug: https://developercommunity.visualstudio.com/content/problem/465815/msbuildextensionspath32-is-not-added-to-system-var.html