-
Notifications
You must be signed in to change notification settings - Fork 337
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
Create DSC file from existing computer #685
Comments
This! Use cases are more than just getting configuration of current machine to clone for others. It's also good to have some kind of UI to compare your current config against the file. So you know for example, what tools you are missing from that or what you have out of date. I would love some kind of UI that I could toggle from all the installed stuff on my computer, select git configs etc. Then go to other machine and do the same - add more stuff that was missing from other computer to config file. And then have one config file, I can deploy across my dev team, and get machines synced up. |
I don't think a separate UI is needed. A way to export to a text file will work well. It could be yaml or json. Then you could use diff and merge, or whatever tools you want to compare and edit them. That is a Unix style way to work. I think it is the best for this task. |
We'd have some type of visual UX i'd imagine but there would be an config file that would be yaml so we could leverage winget configuration |
Adding further support for this scenario. I am setting up 20 machines for a show. I have to install Visual Studio, .NET, lots of SDKs, and more. Once I get one machine setup using Winget or Dev HOme, it would be great to just export everything I just did and tell the other 19 machines to do the same thing. I've already saved a ton of time using Winget and Dev Home, but I'll save a lot more if I don't have to create my own .DSC file :) |
Suggested new feature or improvement
I have my existing computer, please help me create a DSC file so it can be used as a base / restore point.
Scenario
No response
Additional details
No response
The text was updated successfully, but these errors were encountered: