Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GetMSBuildExecutionPath not finding MSBuild.exe #324

Open
rvdginste opened this issue May 26, 2012 · 1 comment
Open

GetMSBuildExecutionPath not finding MSBuild.exe #324

rvdginste opened this issue May 26, 2012 · 1 comment

Comments

@rvdginste
Copy link

On one of my machines OpenWrap gets confused when trying to find the MSBuild execution path. It looks in @"%windir%\Microsoft.NET\Framework" for directories that start with "v"... However on that system there is also a folder "VJSharp" which is selected. Because it is given as an argument to Version, this fails.

So I would suggest to either use a more strict regular expression to find the executable, or check the registry. It seems there are registry keys of the form: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0\MSBuildToolsPath" that contain the correct path of MSBuild. Maybe it's better to use those if available and fall back to the other method if not?

@serialseb
Copy link
Member

The reg is probably the right approach, would be good to have that combined with selecting the version of msbuild and toolsversion is in use.

Seb

On 26 May 2012, at 13:49, "Ruben Vandeginste" reply@reply.github.com wrote:

On one of my machines OpenWrap gets confused when trying to find the MSBuild execution path. It looks in @"%windir%\Microsoft.NET\Framework" for directories that start with "v"... However on that system there is also a folder "VJSharp" which is selected. Because it is given as an argument to Version, this fails.

So I would suggest to either use a more strict regular expression to find the executable, or check the registry. It seems there are registry keys of the form: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0\MSBuildToolsPath" that contain the correct path of MSBuild. Maybe it's better to use those if available and fall back to the other method if not?


Reply to this email directly or view it on GitHub:
#324

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants