Noopman.Setup01.PC.ps1

<#
This file sets up the base line for a new PC.

Command line for scripting and development follows in another file,
and tools in yet another file.
#>

# --------------------------------------------------------------------------------------
# Ensure you can install remote modules.

Get-Executionpolicy -List

Set-Executionpolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser -Force

Get-Executionpolicy -List

Set-Executionpolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine -Force # Admin required

Get-Executionpolicy -List # Now you can execute signed remote things!

# --------------------------------------------------------------------------------------
# Winget is a command-line package manager for Windows 10.
# Read about it by executing this line:
explorer https://learn.microsoft.com/en-us/windows/package-manager/

# If the following command does not work on your system
# either you are on Windows 10 and can install winget (maybe you need to upgrade Windows 10),
# or you really need to upgrade your OS!
winget

# To install winget go here and choose the "App Installer" from the Microsoft Store:
explorer https://apps.microsoft.com/store/search/App%20Installer

winget # verify winget is installed - this line should execute

# --------------------------------------------------------------------------------------
<# Windows Terminal
 # Windows Terminal is a new, modern, fast, efficient, powerful, and
 # productive terminal application for users of command-line tools and
 # shells like Command Prompt, PowerShell, and WSL.
#>
explorer https://docs.microsoft.com/en-us/windows/terminal/

# Do I already have Windows Terminal?
wt

# If not then install it!
winget install Microsoft.WindowsTerminal

wt # verify Windows Terminal is installed

# --------------------------------------------------------------------------------------
<# PowerShell 7
  # PowerShell 7 is a cross-platform (Windows, Linux, and macOS) automation
  # and configuration tool/framework that works well with your existing
  # tools and is optimized for dealing with structured data (e.g. JSON,
  # CSV, XML, etc.), REST APIs, and object models. It includes a command-line
  # shell, an associated scripting language and a framework for processing
  # cmdlets.

# You can execute this line below to read about installing PowerShell 7, even if it is in a comment!
explorer https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-core-on-windows
#>

$PSVersionTable # Check your PS version. Is it < 7?

# These --override options do not seem to work on Winodws 10. Windows ® Installer. V 5.0.19041.2193.
# Maybe it only works on Winodws 11?
winget install --id Microsoft.Powershell --source winget --override '/SILENT /mergetasks="addopenherecontextmenus,addrunwithpowershell7contextmenu"'

# Note: the overrides '/SILENT /mergetasks="addopenherecontextmenus,addrunwithpowershell7contextmenu"'
#       is convenient to add the "Open PowerShell 7 here" and "Run with PowerShell 7" context menu items.

# This is a clean install where you won't get the options checked by the override.
winget install --id Microsoft.Powershell --source winget

# The other option is to browse to the site just above and download the MSI!
# When you do you can check the right boxes during install yourself!

exit # restart your terminal

wt # start Windows Terminal

$PSVersionTable # Check your PS version. This can be 5.1 or similar.

# PowerShell installer adds to the PC environment settings.
# For the next command to work you need to sign out and back into Windows.

pwsh # Start PowerShell 7 in your terminal session.

$PSVersionTable # Now your PS version should be 7.3.0 or higher.

# --------------------------------------------------------------------------------------
<# wt configuration

* In wt choose the "arrow" on the top line and "settings", or type ctrl+,
* Default profile: 'PowerShell' (which means Power Shell 7, instead of Windows Powershell, the old version).
* Default terminal application: Windows Terminal
* Launch mode: I prefer maximized.
* Save settings! (I often forget this step.)

# --------------------------------------------------------------------------------------
# Note: From now you always use wt and a PS7 session! Power Shell 5 is old news.

# --------------------------------------------------------------------------------------
<# Git
Git is a free and open source distributed version control system
designed to handle everything from small to very large projects
with speed and efficiency.
#>
git --version # check if git is installed

winget install Git.Git # install git

# Again now you need to sign out and back in again!

git --version # verify git is installed

# Configure your git user email and name:
git config --global user.email "you@example.com" # Note: Replace with your email!
git config --global user.name "Your Name" # Note: Replace with your name!

# Alternatively, install Git manually by downloading and installing git:
explorer https://git-scm.com/download/win

# --------------------------------------------------------------------------------------
# Set up a location for where you always keep code (IaC or otherwise).
$codeDir = 'D:\'
New-Item -ItemType Directory -Path $codeDir
Set-Location $codeDir

# --------------------------------------------------------------------------------------
# PowerShell profile

# Open or create a profile file for your custom settings.

# On Windows 10 you need to first create the file:
if (!(Test-Path -Path $profile)) { New-Item -ItemType File -Path $profile -Force }

notepad $profile

# Insert the following two lines in the file and save.
$codeDir = 'D:\'
Set-Location $codeDir

# Reload your PS session profile.
. $profile

# Your command line will now always start in this location convenient location!

# By the way. There is probably multiple profile files on your computer:
$profile | Format-List -Force
# Check to see what profile file you use now:
$profile

# ------------------------------------------------------------------
<# Visual Studio Code (VS Code)

Visual Studio Code is a code editor redefined and optimized for
building and debugging modern web and cloud applications.

Note: This is the chicken and egg situation I mentioned above.
VS Code does not need to go in this early, but it makes sense in context.
#>

# Execute this command to go to the site for VS Code:
explorer https://code.visualstudio.com/

# Do I already have Visual Studio Code? Test this:
code # Should start Visual Studio Code

# If not then install it!
winget install Microsoft.VisualStudioCode --source winget --override '/SILENT /mergetasks="!runcode,addcontextmenufiles,addcontextmenufolders"'

<# VS Code installation options:

# 1) Install VS Code manually from the site just above:
explorer https://code.visualstudio.com/

# 2) VS Code download from the command line and launch the install:
New-Item -ItemType Directory -Path 'c:\temp'
Invoke-WebRequest -Uri 'https://code.visualstudio.com/sha/download?build=stable&os=win32-x64-user' -OutFile 'c:\temp\vscode.exe'
c:\temp\vscode.exe # Run this!
#>

# Again now you need to sign out and back in again!

code # verify VS Code is now installed!

# Add an extension to VS Code for PowerShell (more exetensions later):
code --install-extension ms-vscode.powershell

# --------------------------------------------------------------------------------------
<# Clone these scripts from GitHub!

Now that you have git on your system, you can clone my repo
with my setup scripts, including this one!
#>
Set-Location $codeDir # Go to your code directory

# Clone my public GitHub repo:
$repoName = 'I.CMD.you.to.develop.fast.in.Azure'
git clone "https://github.com/noopman/$repoName.git"

Set-Location "$codeDir\$repoName"

# Open the folder in VS Code...
code -n .
# And then open this file to the right line:
code -r -g .\Noopman.Setup01.PC.ps1:212

# Let's continue here! ;~)

# ------------------------------------------------------------------
# Visual Studio Code Configuration time!

<# Change an incorrect default in VS Code!

The biggest problem with VS Code is that it has a "wrong" default setting.

When you execute code from a script file in VS Code
the default behaviour is to focus on the command prompt.

This is quite annoying when you want to use F8 to execute a partial script.

If you have your cursor on a given line and hit F8 VS Code
PowerShell extension will execute that line.

In VS Code, try below by putting your cursor on the following line and hitting the F8 button:
#>
Write-Host 'This line will execute and focus is now in the console window.'
<#
Standard behaviour when executing the above is that this text window loses focus.
Focus is set to the console window.
Now you have to click back into this file to continue developing a script.
That's annoying.

Instead configure VS Code with this setting!
Open the VS Code settings file and add the following:

"powershell.integratedConsole.focusConsoleOnExecute": false,

When tesing on Windows 10, I had to also exit Code and reopen it for the new setting to apply.

Now execute the next line, or two lines if you like by selecting the text of the lines:
#>
Write-Host 'This line will execute and focus remains in this window!'
Write-Host 'You can either execute the line where your cursor is blinking or a selection of script.'

# ------------------------------------------------------------------
<# VS Code Extensions:

Note: I use the command line to install extensions, but you can also
install them from the Extensions tab in Visual Studio Code.
#>

# You can read about all extensions here:
explorer https://marketplace.visualstudio.com/VSCode

code --install-extension AzurePolicy.azurepolicyextension --force
code --install-extension ms-azuretools.vscode-azureresourcegroups --force
code --install-extension ms-azuretools.vscode-azurestorage --force
code --install-extension ms-azuretools.vscode-azurevirtualmachines --force
code --install-extension ms-azuretools.vscode-bicep --force
code --install-extension ms-azuretools.vscode-docker --force
code --install-extension ms-dotnettools.vscode-dotnet-runtime --force
code --install-extension ms-vscode-remote.remote-containers --force
code --install-extension ms-vscode-remote.remote-ssh --force
code --install-extension ms-vscode-remote.remote-ssh-edit --force
code --install-extension ms-vscode-remote.remote-ssh-explorer --force
code --install-extension ms-vscode-remote.remote-wsl --force
code --install-extension ms-vscode-remote.vscode-remote-extensionpack --force
code --install-extension ms-vscode.azure-account --force
code --install-extension ms-vscode.azurecli --force
code --install-extension ms-vscode.vscode-node-azure-pack --force
code --install-extension ms-vsliveshare.vsliveshare --force
code --install-extension ms-vsonline.vsonline --force
code --install-extension msazurermtools.azurerm-vscode-tools --force
# code --install-extension ms-vscode.powershell # Already installed above.

# --------------------------------------------------------------------------------------
<# Ensure Windows Terminal (wt) and Visual Studio Code Teminal use the exact same PowerShell 7 profile.
 # This is a convenience to ensure that you have the same settings in both terminals.
 # The following two files fetched by the $profile command should be the same:
#>
wt # Start Windows Terminal
$profile # run in the command line in Windows Terminal.
code # Start Visual Studio Code
$profile # run on the pwsh command line in VS Code.
# Are the two terminal instances using the same profile?

# Note: now you are in VS Code and you can execute

# --------------------------------------------------------------------------------------
<# PSReadLine
 # PSReadLine is a module that provides command line editing features in the PowerShell console host.
explorer https://learn.microsoft.com/en-us/powershell/module/psreadline/
#>
Install-Module PSReadLine -Force -SkipPublisherCheck -AllowPrerelease
# Check the install:
Get-Module | Where-Object { $_.Name -EQ 'PSReadLine' } | Format-Table Name, Version
# This is the folder where console history will be stored that is used by PSReadLine:
explorer "$env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine"

# --------------------------------------------------------------------------------------
# CaskaydiaCove NF or Cascadia Code PL fonts.
# These are good looking fonts we will use on the command line.

# See releases:
explorer https://github.com/ryanoasis/nerd-fonts/releases/
# Get this:
explorer https://github.com/ryanoasis/nerd-fonts/releases/download/v2.2.2/CascadiaCode.zip
# Download and extract zip.
# Install the fonts on the computer.

# See releases:
explorer https://github.com/microsoft/cascadia-code/releases #PL = Power Line
# Get this:
explorer https://github.com/microsoft/cascadia-code/releases/download/v2111.01/CascadiaCode-2111.01.zip
# Download and extract zip.
# Install the fonts in the ttf folder on the computer (I don't install all fonts in the "static" folder).

# --------------------------------------------------------------------------------------
# Configure WT to use the new font: Two options!
<# Option 1: Graphically

* Go to: WT > Settings > Profiles > Default > Font
* Set CaskaydiaCove NF as the font face.
* Set 14 as the font size. I prefer a slightly larger font. You choose one that suits you!
* Save settings!
#>
<# Option 2, using the config file, which I prefer:

* Open WT settings and in the bottom left select "Open JSON file".
* Add the font to the default profile and select a font size you like.
"profiles": {
        "defaults": {
            // Put settings here that you want to apply to all profiles.
            "font":{
                "face": "CaskaydiaCove NF",
                "size": 14
            }
        },
* Save the config file.
#>

<# Configure terminal in VS Code to use the new font!

* In VS Code click on the gear icon bottom left!
* Choose settings!
* Top right choose the file-looing icon to "Open Settings (JSON) - VS Code settings file.
* Add the following and save - to set the right font and a good font size.

"terminal.integrated.fontFamily": "CaskaydiaCove NF",
"terminal.integrated.fontSize": 14

#>

# --------------------------------------------------------------------------------------
<# While we are in the VS Code JSON config,
   here some other "good" settings I enjoy:
{
    "explorer.confirmDelete": false,
    "editor.formatOnPaste": true,
    "editor.tabSize": 2,
    "editor.insertSpaces": true,
    "git.autofetch": true,
    "git.confirmSync": false,
    "workbench.editor.highlightModifiedTabs": true,
    "files.trimFinalNewlines": true,
    "terminal.integrated.defaultProfile.windows": "PowerShell",
    "editor.fontFamily": "'Cascadia code'",
    "powershell.integratedConsole.showOnStartup": false,
    "editor.inlineSuggest.enabled": true,
    "workbench.startupEditor": "none",
    "git.enableSmartCommit": true,
    "git.smartCommitChanges": "tracked",
    "editor.formatOnType": true,
    "terminal.integrated.scrollback": 25000,
    "editor.linkedEditing": true,
    "editor.fontLigatures": true,
    "markdown.preview.fontSize": 16,
    "debug.console.fontSize": 16,
    "editor.fontSize": 16,
    "files.autoSave": "afterDelay",
    "azureResourceGroups.groupBy": "resourceGroup"
}
#>

# --------------------------------------------------------------------------------------
<# Terminal icons
 # Terminal-Icons is a PowerShell module that adds file and folder icons
 # when displaying items in the terminal.
 # This relies on the custom fonts provided by Nerd Fonts.
explorer https://github.com/devblackops/Terminal-Icons
#>
Install-Module -Name Terminal-Icons -AllowClobber -Force

notepad $profile # Open your profile file.
# Insert the next line in your profile and save:
Import-Module -Name Terminal-Icons

. $profile # Reload your profile in the current session.

# Check that the terminal icons are working.
Get-ChildItem # this should show file and folder icons that look really nice and colourful!

# --------------------------------------------------------------------------------------
<# oh-my-posh
 # oh-my-posh is a theme engine for your shell. It allows you to use
 # themes created by the community or create your own.
 # This relies on the custom fonts provided by Nerd Fonts.
explorer https://ohmyposh.dev/docs/installation/windows
#>
# Either
winget install JanDeDobbeleer.OhMyPosh --source winget
<# Or download and install manually.
Set-ExecutionPolicy Bypass -Scope Process -Force; Invoke-Expression ((New-Object System.Net.WebClient).DownloadString('https://ohmyposh.dev/install.ps1'))
#>

# Restart terminal

# Where is oh-my-posh installed?
(Get-Command oh-my-posh).Source

# What shell am I running?
oh-my-posh get shell # should be 'pwsh' for PowerShell 7.

# Here is how to install a prompt theme. I show how to install my theme below.
explorer https://ohmyposh.dev/docs/installation/prompt

# Install my theme
Copy-Item D:\I.CMD.you.to.develop.fast.in.Azure\oh-my-posh\noopman.omp.json (Get-Item $env:POSH_THEMES_PATH)

# To set the noopman theme as your default:
notepad $profile
# Add this to the profile file and save
oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH\noopman.omp.json" | Invoke-Expression
# Reload the profile in your terminal window
. $profile

# If (when) you don't lke my theme,
# pick and potentially modify any existing theme you fancy:
Get-Command -Module oh-my-posh-core # You find a Get-PoshThemes command.
Get-PoshThemes # This will show you all available themes and what they look like using your current session.

# You can also browse themes here:
explorer https://ohmyposh.dev/docs/themes

# --------------------------------------------------------------------------------------
<# Finally a tip how to run VS Code in full code window mode:

* In VS code while focused on a code file, use this shortcut to maximize the code window:

ctrl + k, z # (hold crtl and press k. then release the keys and press z)

* Toggle terminal window:

ctrl + j

* Toggle left windows:

ctrl + b

* Open file explorer window:

ctrl + e

* Open the command palette with:

ctrl + shift + p

#>

# --------------------------------------------------------------------------------------
<# Azure PowerShell Az
 # Az is the PowerShell module for Microsoft Azure.
 # It provides cmdlets for managing resources in Azure.
explorer https://learn.microsoft.com/en-us/powershell/azure/what-is-azure-powershell

Note: I consider Az PowerShell one of my fundamental and most used tools.
      Azure CLI is also great, and I use both equally.
#>
Install-Module -Name Az -Scope AllUsers -Repository PSGallery -Force

# Now continue with the next step: Install Azure CLI and Azure PowerShell modules.
code -r -g .\Noopman.Setup02.CMD.ps1:1

###END####################
return

# The repo where you can get this script is here:
explorer https://github.com/noopman/I.CMD.you.to.develop.fast.in.Azure

# Please enjoy, reuse, and share! ; ~) Give credit to @noopman!

# Thanks for reaching this far. I hope this is useful to you! /noopman