Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VS2017: separate layout options in a separate file #4

Open
rismoney opened this issue Jun 21, 2018 · 3 comments
Open

VS2017: separate layout options in a separate file #4

rismoney opened this issue Jun 21, 2018 · 3 comments

Comments

@rismoney
Copy link
Contributor

recommended by @majkinetor

  • easier to customize without changing update.ps1
  • link to see all available packages
@gep13
Copy link
Member

gep13 commented Jun 21, 2018

@rismoney have you seen this:

https://github.com/jberezanski/ChocolateyPackages/blob/master/chocolatey-visualstudio.extension/EXAMPLES.md

Is what you are suggesting in this issue similar to what is possible using that package?

@rismoney
Copy link
Contributor Author

i think that stuff is great there, but it is far too abstracted and/or segmented.

Many enterprises just want a prefab set of workloads. The updater side can include as many workloads as you want, but the installer must always be a subset. I maintain 1:1, but it's trivial to create "spinoff" packages or parameter packages using the same source, and a different json, but I avoided that and created a standard install after polling the devs to provide a workload spec. I think the alternate json files approach provides a better wrapper versus micromanaging workloads in an enterprise. If you really had to partition your devs, i'd prefer groups of workloads versus individual specification.

Finally while those scripts/packages handle creating layouts and whatnot, my goal was also not to treat VS like a snowflake, and instead manage it like any other package. Thats why I put the package assembly into AU. Anytime a new version is published, it is easily consumable via choco upgrade. Totally hands off.

@gep13
Copy link
Member

gep13 commented Jun 22, 2018

@rismoney thanks for getting back to me. That makes perfect sense, I just wanted to make sure that we were avoiding duplication of effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants