You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes you may want to compare tools & functionality in a side|Side manner without needing a huge amount of space to do so
This would be a nicer experience if for each toy there was indivual installer packages.
Should align by publishing artifacts including .exe / MSI / MSIX / zips for individual toys
Should potentially also allow current installer to show a UI for installing only tool x,y,z & also take a configuration file or cmdline options to do so.
Scenario when this would be used?
Smaller purpose Operating installations for different tasks
I.E - having a clean os for PowerShell Dev, Email & Doc authoring, Blogging, Browsing, Administrative tasks etc
This aligns with industry practices where the desire to lower potential Security risks by only having what you need installed on a box
Supporting information
Look at Tiny11 - this rips out lots of things from end Windows installs
Winget Configuration / DSC for OS configs including app installs etc
Check out a number of installers like SQL Server installer & PowerShell DSC Resources (SharePoint another good example in DSC) for more inspiration
The text was updated successfully, but these errors were encountered:
other consideration, I only use image resizer from powertoys because there were too many system wide bugs having all functionality turned on (I use groupy from stardock, sharex etc)
Description of the new feature / enhancement
Sometimes you may want to compare tools & functionality in a side|Side manner without needing a huge amount of space to do so
This would be a nicer experience if for each toy there was indivual installer packages.
Should align by publishing artifacts including .exe / MSI / MSIX / zips for individual toys
Should potentially also allow current installer to show a UI for installing only tool x,y,z & also take a configuration file or cmdline options to do so.
Scenario when this would be used?
Smaller purpose Operating installations for different tasks
I.E - having a clean os for PowerShell Dev, Email & Doc authoring, Blogging, Browsing, Administrative tasks etc
This aligns with industry practices where the desire to lower potential Security risks by only having what you need installed on a box
Supporting information
Look at Tiny11 - this rips out lots of things from end Windows installs
Winget Configuration / DSC for OS configs including app installs etc
Check out a number of installers like SQL Server installer & PowerShell DSC Resources (SharePoint another good example in DSC) for more inspiration
The text was updated successfully, but these errors were encountered: