Using Powershell in C# [.NET 6] [duplicate]

Question

I migrated from .NET Framework 4.8 to .NET 6.

System.Management.Automation.PowerShell.Create();

now returns null.

Packages

Is there a new package i need to reference or other solution?

This is happening because of a version of miss-match. Can please share the exception if any — vwadhwa3
– vwadhwa3, Commented Jan 18, 2022 at 20:30
Nevermind stackoverflow.com/questions/51733481/… helped me. — rubgra
– rubgra, Commented Jan 18, 2022 at 20:34
At a minimum you need System.Management.Automation (everything contained in that package is also included in the SDK) — Mathias R. Jessen
– Mathias R. Jessen, Commented Jan 18, 2022 at 20:37

mklement0 · Accepted Answer · 2022-01-18 20:40:23Z

3

Removing the old References and adding the NuGet package Microsoft.PowerShell.SDK solved this issue.

edited Jan 18, 2022 at 20:40

mklement0

452k68 gold badges727 silver badges986 bronze badges

answered Jan 18, 2022 at 20:33

rubgra

2273 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

mklement0 Over a year ago

An overview of all PowerShell SDK-related packages can be found in this answer.

mklement0 Over a year ago

Note, however, that the package you mention is for creating stand-alone PowerShell (Core) applications, whereas the PowerShellStandard.Library package is for creating modules and PowerShell hosts that run from within PowerShell - and the latter package is designed to work in PowerShell (Core) sessions too.

Post Impatica Over a year ago

I wasted time trying to use the powershellstandard.library. Because the SDK was so large and I was skeered to use it. This article may help: stackoverflow.com/questions/51733481/…

Collectives™ on Stack Overflow

Using Powershell in C# [.NET 6] [duplicate]

1 Answer 1

3 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Linked

Related