Execute command in external computer in .NET core

Question

0.00/5 (No votes)

See more:

want to execute cmd command with arguments in my .NET Core application. The problem is that I have to call it in external computer. I now IP, user, password of VM, the command that's needed to execute and its arguments. However I have trouble finding how to actually do it.

What I have tried:

I found example for .NET framework How to execute a command in a remote computer? but I've read that

using System.Management;

has not been migrated from .net framework to .net core. Is there other alternative how to do that?

Posted 24-May-20 6:09am

Member 12885549

Updated 24-May-20 11:59am

Add a Solution

Comments

Maciej Los 25-May-20 4:22am

Why do you need to execute command on remote computer?

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)

Dave Kreskowiak · Answer 1 · 2020-05-24T12:00:00

I don't think you have any options to that in .NET Core.

The System.Management namespace will only work on Windows.

Now, if the Process you want to start is an interactive one, meaning you're expecting the process to show up on the desktop of the user logged into the remote machine, that's not going to happen. You cannot start an interactive process remotely because it would be a huge security risk. The process would still start, but it'll just sit there forever, waiting for input that will never show up.