The following gist showed a failure of the svmPowerShell installer on the Windows platform.
The root cause was due to the installers running under PowerShell 2.0 and by association .NET 2.0. There are calls to .NET within the installers and the signatures of those calls require .NET 4.
The easiest solution to this is to state a pre-requisite for PowerShell 4 and .NET 4 on the machine running the svm installer.
The following gist showed a failure of the
svm
PowerShell
installer on the Windows platform.The root cause was due to the installers running under PowerShell 2.0 and by association .NET 2.0. There are calls to .NET within the installers and the signatures of those calls require .NET 4.
The easiest solution to this is to state a pre-requisite for PowerShell 4 and .NET 4 on the machine running the
svm
installer.The wiki will be updated to reflect this.