If you’ve attempted to install the Docker Tools for Visual Studio – August Release, starting on Friday August 21st, you may have fallen into the trap of not reading the descriptive text below that explains what we should have done for you.
Quick answer: Follow the detailed instructions for installing Microsoft ASP.NET and Web Tools 2015 (Beta6) – Visual Studio 2015
Longer Answer – what happened:
In addition to supporting Windows Containers, the August release of Docker Tools for Visual Studio was updated to support Visual Studio 2015 RTM. Some changes were made to Web Tools Essentials between RC and RTM that we didn’t get everything checked in and complete in time. As a result, to make the Docker Tools work with ASP.NET publishing we had to take an updated version of WTE. Rather than have one off versions of WTE, and since Docker Tools for Visual Studio targets developers working with ASP.NET 5, we aligned our install experience with the Beta releases of WTE.
When we released the 0.6 release last Wednesday, we were chaining in the WTE beta 6. If you were on a full English version of Visual Studio, life was good. A nice simple, (albeit long) experience. Unfortunately, since the preview of Docker Tools for VS isn’t yet localized, developers with non-English versions of VS would get in a broken state as we weren’t chaining in the language packs for WTE. To avoid others falling into this broken trap, last Friday we pulled WTE from the Docker Tools installer, and placed a nice little ToDo link in the download page of the extension. It was a quick decision we heavily debated as there were concerns others would fall into this trap, and we apologize.
We are actively working to fix the install experience in two phases:
- Phase 1 – We will ship an update to the Docker Tools for Visual Studio that will block the install until you first install the proper beta version of WTE. This will also include a few bug fixes that we’ve found since last Wednesday. We hope to have this out soon.
- Phase 2 – Docker Tools got caught in this spot as the Web Publishing Experience doesn’t have an extensibility model, which meant we needed to ship all of WTE just to get the Docker hook in. The current plan is to have this extensibility point in place for Visual Studio Update 1. This will allow us to easily rev the Docker Tools without having to redistribute updates to WTE.
Thanks for your patience,