![]() NET Framework 4.6.1 support Windows SDKs, ATL support, etc.: There are also optional individual components to install. An optional workload “Web development build tools”.An optional workload “Visual C++ build tools”.A built-in (non-optional) set of components to build MSBuild-based projects (for example managed projects).Once you install them on a clean machine, you will notice that they provide only the following: The Visual 2017 Build Tools can be downloaded from here. Incidentally my MZ-Tools solution has both type of projects. They can be used to build either managed (C#, VB.NET, etc.) projects or native (C++) projects. ![]() They are a lightweight version of Visual Studio 2017 without the IDE (devenv.exe executable). As part of that process, I realized than rather than installing Visual Studio 2017 Community edition on the server, I could use the Visual Studio 2017 Build Tools that were thought, well, for build servers that don’t need the overhead of a Visual Studio 2017 installation. As I explained in the post Migrating the build of a VSIX project to a build server if you are a solo developer, I am taking the steps to build my MZ-Tools extension on a build/release server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |