Dismiss Notice

Register now to be one of the first members of this SharePoint Community! Click here it just takes seconds!

Dismiss Notice
Welcome Guest from Country Flag

Cloning Your VS 2017 Packages

Discussion in 'Official Microsoft News' started by Greg Duncan, Apr 3, 2017.

Thread Status:
Not open for further replies.
  1. Greg Duncan

    Greg Duncan Guest

    Blog Posts:
    So, you've just installed VS 2017. Now you want to "copy" that setup and share what you installed with your coworkers, say you're trying to create a standard work or class setup...

    How do you capture what you installed? You're sure there's some kind of command line switch or something, some way to export your currently installed VS 2017 setup/package/workload?


    There is a cool new VS 2017 Setup API, Setup Configuration, though, with code samples and everything. Maybe that can be used?


    Today's quick and dirty project from Tim Sneath uses the Setup Configuration API to capture and export your currently installed packages, generating the command line parameters that you can use to install a like looking VS setup on another PC.


    Clones a Visual Studio 2017 installation so it can be reproduced on another machine. Run this on a machine that already has Visual Studio 2017 installed, and it will interrogate the instance of Visual Studio to identify what workloads and components were selected, and attempt to create a command line that recreates the same installation.



    • Very limited testing done so far
    • Doesn't identify language packs installed
    • Assumes only one VS2017 instance on the machine
    • While it recognizes component groups, it also identifies individual components that are part of the component group as if they've been individually selected.
    • Code isn't very pretty yet



    ... [Click through for the repo]

    Follow @CH9
    Follow @coding4fun
    Follow @gduncan411


    Continue reading...
Thread Status:
Not open for further replies.

Share This Page

LiveZilla Live Chat Software