Execute a PowerShell command on the Server-Side in ASP.net

Question

1.00/5 (1 vote)

See more:

ASP.NET

PowerShell

Is it possible to execute a PowerShell command on the Server-Side in ASP.net?

Posted 16-Jul-15 11:27am

teledexterus

Add a Solution

Comments

Sergey Alexandrovich Kryukov 16-Jul-15 18:13pm

Why? Really, why? I'm just curious.
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2015-07-16T12:12:00

I doubt it. The server and Web applications are normally executed in a sandboxed environment which blocks the access to the server host's system beyond what is normally needed for Web operation; even the access to the file system is limited by the root directory set up for the site.

For that matter, even normal execution of .ps1 scrip files by a privileged user is by default limited, one would need to load the PowerShell IDE and interactively issue the command granting this permission. This is not related to Web operations but tells the tale.

After all, think at this: PowerShell is, well… powerful. Imagine how huge would be your security threat if you expose its operation to the Web application user. I would strongly advise you just to forget about the thought.

Perhaps is you share with us your ideas and your ultimate goals, you can get more positive advice. For example, if you just need to use WMI, you could simply use using System.Management.Automation;… and… then directly deal with the permissions and possible permission exceptions.

—SA