choco export -- for going forwards

[brothers-morrison]

I love this idea BTW and have/had done something similar just to keep track of my choco scripts, but yours is nicer.
Thanks for posting the repo.

Idea:
Seems like this might now be better able to be done via a "master" list exported from a single vanilla install.
https://stackoverflow.com/questions/43167087/how-to-get-a-list-of-packages-from-one-machine-and-install-in-another-with-choco

So my proposal/idea: (take it or leave it)

1. choco export (to VanillaMasterList_DEV.xml) one time
2. Save exported file into this repo
3. Script then just pulls whatever is in the export file (which is slighly more easily edited by just installing or uninstalling from vanilla computer/vm, especially in cases where user(s) have completely different setups, already set up on some other machine).
   In this case it also scales to N number of different setups, 1x for each file (HR department, Finance, IT, etc...)
4. Adds/Removes from the file can then be done through existing commands to choco install/uninstall on a "Vanilla" computer, followed by another export to update the VanillaMasterList_DEV.xml
5. Could have 1x file for dev machines, 1x file for regular users, and N other files for different configurations