-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Standalone Build Tools update #480
Comments
If there's any workaround in the meantime (such as installing the original build tools and copying stuff from a VS machine), we'd be interested to know. We're keen to start using the new features, but we're nervous about some of the issues reported in the original release of the compilers :( |
I think managing the build tools on a server is a larger problem then just the MS Build Tools currently. |
Do you know how likely this might be addressed in time for Update 2 RTM? If it's unlikely and we need to start adding the NuGet packages to our projects, it'd be good to get a head-start! |
@DanTup We've made the internal changes and daily builds of Update 2 RC are producing this installer. We do expect it to be released with RC and with RTM Update 2. |
@rainersigwald Excellent! Thanks for the update :) |
Update 2 RC has a Build Tools package available: http://go.microsoft.com/fwlink/?LinkId=518023. Please let us know if you try it and see any problems since the Update 2 RTM release is fast approaching. EDIT: updated link. |
I'd be nervous about installing the RC on our production build server and don't easily have another way to test this; though I have faith in your ability to build the installer and presume the compilers will get a good testing by others :D |
That said; I'm presuming installing this would cause our builds to automatically use it; if it would need to us to change which MSBuild we call and wouldn't affect anything else then maybe we can test it (we're currently using a pre-2015 MSBuild (12?) and never installed the original version of these build tools). |
@DanTup Ah, that's interesting. I too would be nervous about applying the RC in production. Note that AFAIK the only way to use the updated Roslyn across the board would be to switch to MSBuild 14 (with Update 2)--MSBuild 12 should be untouched by this installation. |
Visual Studio 2015 Update 2 RTM is now available. Can we expect that an updated MSBuild will be released soon? |
The updated tools appear to be here :) https://www.visualstudio.com/downloads/download-visual-studio-vs#d-build-tools However there's a weird layout issue with that page so you'll have to scroll down to see them! (edit: strangely happens on Chrome on my machine, but not on our buildserver!) |
Maybe the Visual Studio Update 2 release should also mention the Build tools Update 2 and its location. Because its hard to find if you do not know where to look for it. Especially for users that have no idea that this was going to be release together with the update. |
I found the link from this page: https://www.visualstudio.com/en-us/news/vs2015-update2-vs.aspx It's under "Related releases" labelled "Microsoft Build Tools 2015 Update 2" :) |
My bad! Guess my eyes skip over that part :) |
@DanTup the page no longer has the build tools under Related Releases section |
This link still works for me: https://www.visualstudio.com/downloads/download-visual-studio-vs#d-build-tools shows "Microsoft Build Tools 2015 Update 3" However, it did redirect me to a "beta" website which I had to click "Exit" from and then navigate back to the link. Direct download link: https://go.microsoft.com/fwlink/?LinkId=615458 |
It would be nice if Microsoft could indicate in the filename which version it is. |
Is it possible to have MSbuild update 1 and update 3 on same build server? |
@pavnii For Build Tools 2015, no, that's not possible. It is now possible to have multiple copies installed starting with Build Tools 2017. |
People often install Microsoft Build Tools 2015 alone on a build server, to avoid having to manage a full Visual Studio installation. But the latest Build Tools installer is for VS2015 RTM, and there's no way to update it (trying to run the full VS update installer fails because "nothing applicable" is installed).
This is something we can only fix internally, since it's official-release-process related.
The text was updated successfully, but these errors were encountered: