Ggtcf

Is "cogitate" used appropriately in "I cogitate that success relies on hard work"?

Does the US political system, in principle, allow for a no-party system?

Is the differential, dp, exact or not?

Insult for someone who "doesn't know anything"

What is Tony Stark injecting into himself in Iron Man 3?

Is divide-by-zero a security vulnerability?

An Undercover Army

Is there a math expression equivalent to the conditional ternary operator?

How to recover against Snake as a heavyweight character?

How would an energy-based "projectile" blow up a spaceship?

Was it really inappropriate to write a pull request for the company I interviewed with?

Why is there an extra space when I type "ls" on the Desktop?

A vote on the Brexit backstop

Why do we say 'Pairwise Disjoint', rather than 'Disjoint'?

PTIJ: Sport in the Torah

3.5% Interest Student Loan or use all of my savings on Tuition?

What is the purpose of a disclaimer like "this is not legal advice"?

Having the player face themselves after the mid-game

How to install "rounded" brake pads

How to write a chaotic neutral protagonist and prevent my readers from thinking they are evil?

Why isn't P and P/poly trivially the same?

Is it a Cyclops number? "Nobody" knows!

Help! My Character is too much for her story!

Can I negotiate a patent idea for a raise, under French law?

Trying to port existing powershell-depending class library from .NET Framework

1

I have .NET Framework class library with some code using older Powershell:

using System.Management.Automation.Runspaces;
using System.Management.Automation;

//some code executing powershell commands in runspaces and processing results, similar to this:
 var runspace = RunspaceFactory.CreateRunspace();
 using (var powerShell = PowerShell.Create())
 
 powerShell.Runspace = runspace;
 powerShell.Commands.AddScript(psscript);
 results = powerShell.Invoke();
 //process results, etc...
 

I'm trying to port it to .NET Core, using package Microsoft.Powershell.SDK with Powershell Core. It works fine for the most part, but for obvious reasons it can't run legacy powershell commands (add-pssnapin, etc).

This class library is intended to be used on a wide range of machines, some of them requiring those old powershell commands to work and others requiring to use Powershell Core. How do I achieve this?

The only solution I can think of is making two separate projects, one of them for .NET Framework and another for .NET Core, but having two projects with same code(except for 4-5 lines with those old commands) seems like a bad idea. Is there a better way to accomplish this?

c# .net powershell .net-core

share|improve this question

edited 2 days ago

user2363676

asked 2 days ago

user2363676user2363676

6219

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Is this a PowerShell Module (i.e., code that implements Cmdlets or PSCmdlets) or is it something else? Do you really use Snapins (they haven't been around for a while I believe).
  
  – Flydog57
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Flydog57 No, code is just executing powershell commands in runspaces and processes results. Executing commands, howerver, requires old third party snapins in some cases.
  
  – user2363676
  2 days ago
  

  
  
  
  

add a comment | 

1

I have .NET Framework class library with some code using older Powershell:

using System.Management.Automation.Runspaces;
using System.Management.Automation;

//some code executing powershell commands in runspaces and processing results, similar to this:
 var runspace = RunspaceFactory.CreateRunspace();
 using (var powerShell = PowerShell.Create())
 
 powerShell.Runspace = runspace;
 powerShell.Commands.AddScript(psscript);
 results = powerShell.Invoke();
 //process results, etc...
 

I'm trying to port it to .NET Core, using package Microsoft.Powershell.SDK with Powershell Core. It works fine for the most part, but for obvious reasons it can't run legacy powershell commands (add-pssnapin, etc).

This class library is intended to be used on a wide range of machines, some of them requiring those old powershell commands to work and others requiring to use Powershell Core. How do I achieve this?

The only solution I can think of is making two separate projects, one of them for .NET Framework and another for .NET Core, but having two projects with same code(except for 4-5 lines with those old commands) seems like a bad idea. Is there a better way to accomplish this?

c# .net powershell .net-core

share|improve this question

edited 2 days ago

user2363676

asked 2 days ago

user2363676user2363676

6219

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Is this a PowerShell Module (i.e., code that implements Cmdlets or PSCmdlets) or is it something else? Do you really use Snapins (they haven't been around for a while I believe).
  
  – Flydog57
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Flydog57 No, code is just executing powershell commands in runspaces and processes results. Executing commands, howerver, requires old third party snapins in some cases.
  
  – user2363676
  2 days ago
  

  
  
  
  

add a comment | 

I have .NET Framework class library with some code using older Powershell:

using System.Management.Automation.Runspaces;
using System.Management.Automation;

//some code executing powershell commands in runspaces and processing results, similar to this:
 var runspace = RunspaceFactory.CreateRunspace();
 using (var powerShell = PowerShell.Create())
 
 powerShell.Runspace = runspace;
 powerShell.Commands.AddScript(psscript);
 results = powerShell.Invoke();
 //process results, etc...
 

I'm trying to port it to .NET Core, using package Microsoft.Powershell.SDK with Powershell Core. It works fine for the most part, but for obvious reasons it can't run legacy powershell commands (add-pssnapin, etc).

This class library is intended to be used on a wide range of machines, some of them requiring those old powershell commands to work and others requiring to use Powershell Core. How do I achieve this?

The only solution I can think of is making two separate projects, one of them for .NET Framework and another for .NET Core, but having two projects with same code(except for 4-5 lines with those old commands) seems like a bad idea. Is there a better way to accomplish this?

c# .net powershell .net-core

share|improve this question

edited 2 days ago

user2363676

asked 2 days ago

user2363676user2363676

6219

using System.Management.Automation.Runspaces;
using System.Management.Automation;

//some code executing powershell commands in runspaces and processing results, similar to this:
 var runspace = RunspaceFactory.CreateRunspace();
 using (var powerShell = PowerShell.Create())
 
 powerShell.Runspace = runspace;
 powerShell.Commands.AddScript(psscript);
 results = powerShell.Invoke();
 //process results, etc...
 

share|improve this question

edited 2 days ago

user2363676

asked 2 days ago

user2363676user2363676

6219

share|improve this question

edited 2 days ago

user2363676

asked 2 days ago

user2363676user2363676

6219

asked 2 days ago

user2363676user2363676

6219

asked 2 days ago

user2363676user2363676

6219