3 years ago

Category: automation

The addition of the PowerShell Dev Mode to Visual Studio 2019 was a great thing for developers that do their own DevOps. Now we have a proper environment in PowerShell for automating MSBUILD and here’s a technique to make it available to be launched in your current session.

Each edition of PowerShell places its profile script in different places and hosts such as CS Code can define their own profile script when string up the session. To simplify access to the script, there is a build in variable named Profile that has the full path to the script for the current environment.

All of the code above is located in profile_aliases.ps1 and my $Profile script actually looks like this.