36f31cc4b0
* Upgrade to Visual Studio 2022 Upgrade from Visual Studio 2017 to 2022 as suggested on #14. * Also update Docker image references from 2017 to 2022 The following images are renamed: * buildtools2017 -> buildtools2022 * buildtools2017native -> buildtools2022native * buildtools2017web -> buildtools2022web |
||
|---|---|---|
| managed-native-desktop | ||
| native-desktop | ||
| web | ||
| .gitattributes | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| README.md | ||
| SECURITY.md | ||
README.md
Samples
You can install Visual Studio Build Tools into a container to support a consistent, isolated build environment. This repository hosts a number of examples - and is accepting contributions for more, useful examples - you can use to build a container image using Build Tools tailored to your project types and build pipeline. Because these container images can be massive - larger than probably anyone needs - and the permutations of different Windows, Visual Studio, and .NET Framework versions would complicate which version you might need, you are encouraged to use these samples or build on them and publish, if desired, images to your own Docker registry on your LAN or WAN.
Note that Visual Studio Build Tools is licensed as a supplemental license for Visual Studio. Images may only be pushed to repositories to provide pull access to users with a valid Visual Studio license.
Contributing
To contribute your own sample Dockerfiles and optional support scripts, please see CONTRIBUTING.
License
This project and all examples herein are licensed under the MIT license. Visual Studio Build Tools is licensed as supplemental license for Visual Studio.