This script sets up my windows development machine using winget. It was initially used in Windows 11.

• script dev drive creation for node_modules global cache + set global environment variable for it
• script dev drive creation for nuget package cache + set global environment variable for it
• script dev drive creation for c:\code directory mount point

Run these scripts on a new machine in powershell. Note: use a user powershell prompt, unless the script explicitly requires it (the scripts detect if they need admin and will imediatly error if not run with elevated admin permissions).

Make sure scripts are executable with this command

set-executionPolicy -Scope CurrentUser RemoteSigned

.\uninstall-rubbish.ps1

You can customise what is installed by commenting in and out the packages in the package list of this script. Review the list before you execute so that you are familiar with what is being installed. https://learn.microsoft.com/en-us/windows/dev-drive/

.\install-packages.ps1

NOTE: manual setup recomended at this point in time, scripted version doesn't work full.

Dev drives are a new Microsoft Windows feature that can improve build times and performance when coding. This is mostly focused at your code directory, npm cache directory, and nuget package cache directory as they contain thousands of files.

Use the 'About this PC' in control panel to work out what edition of Windows 11 you are running.

• If you are running 'Windows 11 Pro' then you need to manually setup DevDrives listed below
• If you are running 'Windows 11 Pro for Workstations' or 'Windows 11 Enterprise' you should be able to use the script below to setup dev drives.

cd dev-drive-setup
.\setup-devdrives.ps1

If you are manually setting up dev drives using 'Disks & Volumes' Settings app, then you should create these directorys on D: drive or C: drive. (I use a separate D: drive if possible or on desktop so that the OS is left alone. I'm unsure if it actually helps performance or not).

• Nuget Cache directory -> mounted in D:\DevDrives\NugetCache
• Npm Cache directory -> mounted in D:\DevDrives\NpmCache
• Code directory -> mounted in D:\Code

Each directory needs a dev drive setup and mounted. Then you can run these statements to ensure Nuget and Npm cache directories are used by those tools.

# make sure paths are correct for what you have setup
# Run these in an 'admin' terminal powershell window
setx /M NUGET_PACKAGES D:\DevDrives\NugetCache
setx /M npm_config_cache D:\packages\NpmCache

• You need to be using Windows 10 (1807 or higher) or windows 11.
• You need 'App Installer' installed (usually included in base windows install I think, or available on microsoft store)
• Winget https://learn.microsoft.com/en-us/windows/package-manager/
• Enable running of scripts for your current user set-executionPolicy -Scope CurrentUser RemoteSigned

Winget CLI should be available on the system.

Winget has several useful commands

winget search [app-name]

winget install [app-id]

winget info

Several useful options when installing from a script.

winget install --silent [app-name]

• --silent installs hiding any gui or popup confirmations, useful when scripting several installations at once.

Setup Win Dev Drive and mount in c:\code directory for code to go into before cloning code https://learn.microsoft.com/en-us/windows/dev-drive/

You need to have the HyperV powershell module installed to use powershell modules to create VHDX files for dev drives in powershell. And windows 11 doesn't allow you to install just the powershell modules of HyperV. Thus the scripts in this repository explicitly use diskpart to do this setup as the powershell tools for hyperV are often not installed or required or aloud by many organisations.

# Install only the PowerShell module
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Management-PowerShell

# Install the Hyper-V management tool pack (Hyper-V Manager and the Hyper-V PowerShell module)
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All

# Install the entire Hyper-V stack (hypervisor, services, and tools)
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All