You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
rvdginste
added a commit
to rvdginste/openwrap
that referenced
this issue
May 26, 2012
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?
The text was updated successfully, but these errors were encountered: