How to install PowerShell module from .NET application

Question

How to install PowerShell module from .NET application

Volodymyr Dumchykov 56

Hi

I need to install a PowerShell module from my .NET application. I have added Microsoft.PowerShell.SDK nuget package to the project and use PowerShell class to execute Install-Module cmdlet. Unfortunatly the execution failed with the following error:

No match was found for the specified search criteria and provider name 'NuGet'. Try 'Get-PackageProvider -ListAvailable' to see if the provider exists on the system.

As I understood, Microsoft.PowerShell.SDK includes neither PackageManagement nor PowerShellGet module which are required for Install-Module cmdlet.

I'v also tries to install nuget package provider via Install-PackageProvider cmdlet. It failed with the following exception

Unhandled Exception - Message:'The type initializer for 'Microsoft.PackageManagement.Internal.Utility.Plugin.DynamicType' threw an exception.' Name:'TypeInitializationException' Stack Trace:'

Any idias what I do wrong?

Anonymous

2023-12-05T02:47:34.7333333+00:00

Hi @Volodymyr Dumchykov , Welcome to Microsoft Q&A,

Try using "Install-PackageProvider -Name NuGet -Force". Have you installed it?
Volodymyr Dumchykov 56 Reputation points

2023-12-05T08:12:00.64+00:00

Hi @Anonymous

Thanks for the answer, it failed with the following error:

Unhandled Exception - Message:'The type initializer for 'Microsoft.PackageManagement.Internal.Utility.Plugin.DynamicType' threw an exception.' Name:'TypeInitializationException' Stack Trace:' at Microsoft.PackageManagement.Internal.Utility.Plugin.DynamicType.Create(Type tInterface, OrderedDictionary2 instanceMethods, List2 delegateMethods, List1 stubMethods, List2 usedInstances) ...

As I understood it's because PackageManagement and PowerShellGet modules are not installed by Microsoft.PowerShell.SDK package.

After building my application I looked at the content of the output folder and found Modules folder with some modules inside, I suppose Microsoft.PowerShell.SDK includes these modules. I compared this list with list of modules installed by standard PowerShell-7.4.0-win-x64.msi package and found that PackageManagement and PowerShellGet ARE installed by MSI, but are NOT installed by Microsoft.PowerShell.SDK. When I copy the modules to my application modules folder Install-Module completes successfuly.
Matthew Wong 0 Reputation points

2024-10-07T11:48:48.65+00:00

Hi @Volodymyr Dumchykov ,
I am working on a similar issue that requires installing the Nuget Powershell package provider in a .NET project in order to install the necessary module.
I am curious on how exactly you copied the modules to your application modules folder since I can't seem to be able to set it up correctly. It would be really appreciated if you could talk through the key steps briefly (e.g. where to install, code configuration, etc).

Many thanks!
Volodymyr Dumchykov 56 Reputation points

2024-10-20T17:32:27.28+00:00

Hi, Matthew,

Unfortunatly I wasn't able to install a Power Shell module using Microsoft.PowerShell.SDK.

I decided to add the module I needed to my assembly as a resource. My app extract the module to a temp folder and specifies that folder as a value of PSModulePath session variable (using InitialSessionState.EnvironmentVariables property).

1 answer

Your answer

Anonymous

2023-12-05T02:47:34.7333333+00:00

Hi @Volodymyr Dumchykov , Welcome to Microsoft Q&A,

Try using "Install-PackageProvider -Name NuGet -Force". Have you installed it?
Volodymyr Dumchykov 56 Reputation points

2023-12-05T08:12:00.64+00:00

Hi @Anonymous

Thanks for the answer, it failed with the following error:

Unhandled Exception - Message:'The type initializer for 'Microsoft.PackageManagement.Internal.Utility.Plugin.DynamicType' threw an exception.' Name:'TypeInitializationException' Stack Trace:' at Microsoft.PackageManagement.Internal.Utility.Plugin.DynamicType.Create(Type tInterface, OrderedDictionary2 instanceMethods, List2 delegateMethods, List1 stubMethods, List2 usedInstances) ...

As I understood it's because PackageManagement and PowerShellGet modules are not installed by Microsoft.PowerShell.SDK package.

After building my application I looked at the content of the output folder and found Modules folder with some modules inside, I suppose Microsoft.PowerShell.SDK includes these modules. I compared this list with list of modules installed by standard PowerShell-7.4.0-win-x64.msi package and found that PackageManagement and PowerShellGet ARE installed by MSI, but are NOT installed by Microsoft.PowerShell.SDK. When I copy the modules to my application modules folder Install-Module completes successfuly.
Matthew Wong 0 Reputation points

2024-10-07T11:48:48.65+00:00

Hi @Volodymyr Dumchykov ,
I am working on a similar issue that requires installing the Nuget Powershell package provider in a .NET project in order to install the necessary module.
I am curious on how exactly you copied the modules to your application modules folder since I can't seem to be able to set it up correctly. It would be really appreciated if you could talk through the key steps briefly (e.g. where to install, code configuration, etc).

Many thanks!
Volodymyr Dumchykov 56 Reputation points

2024-10-20T17:32:27.28+00:00

Hi, Matthew,

Unfortunatly I wasn't able to install a Power Shell module using Microsoft.PowerShell.SDK.

I decided to add the module I needed to my assembly as a resource. My app extract the module to a temp folder and specifies that folder as a value of PSModulePath session variable (using InitialSessionState.EnvironmentVariables property).

Answer 1

Jens Schmitz 5

Hi @Volodymyr Dumchykov

Couldn't you just start a new PowerShell process and then pass the Install-Module as an argument?

Volodymyr Dumchykov 56 Reputation points

2023-12-05T08:24:21.98+00:00

Hi, @Jens Schmitz

Thanks for the answer! Yes, I can launch a new PowerShell process, but then I should add a requirement to install PowerShell.

Share via

How to install PowerShell module from .NET application

1 answer

Your answer