-
Notifications
You must be signed in to change notification settings - Fork 64
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
Doesn't work with MSBuild 14.0 #170
Comments
Yes If they continue to publish software with hard-coded version numbers in their paths, which I assume they are from your question :) |
I was going to attempt to change it and do a pull request, but I can't get wdm to install on my machine. Couldn't you just inspect the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions for all of the versions installed, pick the greatest one and use that? Then you wouldn't need an update for every new tools version that comes out. |
What's WDM? I believe that's being inspected. The build task-type is completely PR-maintained nowadays as I've migrated 100% to OS X and Linux and mono. I'm still using albacore for everything though ;) If you think inspecting that key gets you the best version number, go for it and PR :) |
I have no idea what wdm is. It shows up as an error when I'm trying to do bundle install. So I take it this won't be fixed unless there is a PR? |
Well, I can probably help you with WDM if you'd post error messages, but no, I'm not going to fix it, because I don't have a Windows machine to reproduce the error on and VS2015 takes three hours just to install according to reliable twitteratis. |
Here's the error message when I do a bundle install. I could do a pull request with untested code, but I don't think that's a good idea, especially since I'm not all that great with ruby.
|
So here's the thread in the wdm library that discusses the issue. The reason you're having trouble is that you're on a too-old version of ruby, mate. |
Get latest msbuild from registry, resolves #170
It looks like there's an array that starts at 12.0 and goes down from there in the build.rb file. Does that array need to have 14.0 added to it in order to build for C# 6.0?
The text was updated successfully, but these errors were encountered: