@Sequoia: launch configs are to do with launching your application in a debugging context (though there may be some other uses I'm not aware of).
Tasks are more about running some toolset such as your build or tests.
I think he wanted to show a migration from running everything yourself from a terminal to running commonly used stuff from a task, to splitting out your debugging use case from your build/test use case.
One thing I don't think he showed was the isBuildCommand and isTestCommand options under tasks.jso. These automatically enable a shortcut of ctrl+shift+B or T to run the build or test commands (see https://code.visualstudio.com/docs/editor/tasks)
I care more about being able to generate a script (say a PowerShell script) rather than sync across devices.
One reason is so I can share the script with colleagues. For example, one developer I work with has avoided upgrading his development machine from Windows 2008 R2 because he worries about how much work is involved in reinstalling Visual Studio.
If I can save scripts from the installer to a file on my disk, I can easily share that with my colleagues. Syncing through my MSDN account is useless to me.
Yes. How you'd do this, and how easy it is, depends on the technology. If the install was created with WiX and is a burn bundle, you can use dark to extract the MSI. Some installs have a command line parameter which extracts the files locally.
Most installs are in fact some type of archive with a wrapper, so something like 7z or IZArc can extract the resources, though it can take some investigation to figure out which is the MSI.
BTW, there is another tool that does the same thing as Orca: http://www.instedit.com/, but has some better capabilities and a more up to date UI. The free version is worth a look (not tried the paid version)
I've had to use Dependency Walker quite a lot to diagnose installs.
It's worth mentioning a few of the gotchas like making sure you match the architecture of Dependency Walker with the architecture of the PE you are analyzing, or that WinSxS typically throws lots of false positives into the list results.