There are a surprising number of ways that you can install PowerShell on a system. Today we'll look at how to install it as a ".NET tool." This approach is not necessary or ideal for everyday use, but it does have some valid use cases and conveniently does not require local admin rights.
Many people have already written about the benefits of using PowerShell's Join-Path cmdlet. Instead of repeating the details, let's review some of the less common tricks, and then look at the differences between Windows PowerShell 5.1 and newer versions of PowerShell.
Through most of the past 20 years of working with Active Directory, I have supported and worked in multi-forest environments. This work has involved one forest being split into 3 forests, a cross-forest migration of Exchange Server (I was spared the first one), and multiple forest consolidation projects. At various points throughout that timeline, I have needed to write PowerShell scripts that rely on either the DNS name, NetBIOS name, or SID of domains in the trust relationship. This information is easy to get using the ActiveDirectory module's Get-ADTrust cmdlet.