On both a work and home machine, when trying to install the module it fails, and given the alias it is failing on, I'm not sure if I want to force it:
Copyright (C) 2016 Microsoft Corporation. All rights reserved.
PS C:\Users\Brendan Grant> Install-Module -Name WintellectPowerShell -Scope CurrentUser
NuGet provider is required to continue
PowerShellGet requires NuGet provider version '2.8.5.201' or newer to interact with NuGet-based repositories. The NuGet
provider must be available in 'C:\Program Files\PackageManagement\ProviderAssemblies' or 'C:\Users\Brendan
Grant\AppData\Local\PackageManagement\ProviderAssemblies'. You can also install the NuGet provider by running
'Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force'. Do you want PowerShellGet to install and import
the NuGet provider now?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
Untrusted repository
You are installing the modules from an untrusted repository. If you trust this repository, change its
InstallationPolicy value by running the Set-PSRepository cmdlet. Are you sure you want to install the modules from
'PSGallery'?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "N"): a
PackageManagement\Install-Package : The following commands are already available on this system:'set'. This module
'WintellectPowerShell' may override the existing commands. If you still want to install this module
'WintellectPowerShell', use -AllowClobber parameter.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:1809 char:21
+ ... $null = PackageManagement\Install-Package @PSBoundParameters
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package],
Exception
+ FullyQualifiedErrorId : CommandAlreadyAvailable,Validate-ModuleCommandAlreadyAvailable,Microsoft.PowerShell.Pack
ageManagement.Cmdlets.InstallPackage
Both machines are running Windows 10 Professional, System.Environment]::OSVersion.Version.ToString() is: 10.0.15063.0 and $PSVersionTable reports:
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.15063.632
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1```
The other PC notes that PSVersion BuildVersion are 5.1.15063.674
Time permitting, I'll try from source a bit later.
Sorry this took a bit. I was forcing the "set" alias in my module to Set-Environment. I've fixed this in the latest release (by no longer being a jerk and setting aliases!). Give it an install now. Thanks!
On both a work and home machine, when trying to install the module it fails, and given the alias it is failing on, I'm not sure if I want to force it:
Both machines are running Windows 10 Professional, System.Environment]::OSVersion.Version.ToString() is: 10.0.15063.0 and $PSVersionTable reports: