Este artículo se tradujo automáticamente. Para ver el artículo en inglés, active la casilla Inglés. Además, puede mostrar el texto en inglés en una ventana emergente si mueve el puntero del mouse sobre el texto.
Traducción
Inglés

Método Process.GetProcessesByName (String, String)

 

Publicado: octubre de 2016

Crea una matriz de nuevos componentes Process y los asocia a todos los recursos de proceso de un equipo remoto que comparten el nombre del proceso especificado.

Espacio de nombres:   System.Diagnostics
Ensamblado:  System (en System.dll)

public static Process[] GetProcessesByName(
	string processName,
	string machineName
)

Parámetros

processName
Type: System.String

Nombre descriptivo del proceso.

machineName
Type: System.String

Nombre de un equipo en la red.

Valor devuelto

Type: System.Diagnostics.Process[]

Matriz de tipo Process que representa los recursos del proceso que ejecutan la aplicación o el archivo especificado.

Exception Condition
ArgumentException

La sintaxis de parámetro machineName no es válida. Puede tener longitud cero (0).

ArgumentNullException

El parámetro machineName es null.

PlatformNotSupportedException

La plataforma del sistema operativo no admite esta operación en equipos remotos.

InvalidOperationException

Hay problemas de acceso a la API del contador de rendimiento que se usa para obtener información del proceso. Esta excepción es específica de Windows NT, Windows 2000 y Windows XP.

Win32Exception

Se ha producido un problema al obtener acceso a una API del sistema subyacente.

Use this method to create an array of new T:System.Diagnostics.Process components and associate them with all the process resources that are running the same executable file on the specified computer. The process resources must already exist on the computer, because M:System.Diagnostics.Process.GetProcessesByName(System.String) does not create system resources but rather associates them with application-generated T:System.Diagnostics.Process components. A processName can be specified for an executable file that is not currently running on the local computer, so the array the method returns can be empty.

The process name is a friendly name for the process, such as Outlook, that does not include the .exe extension or the path. M:System.Diagnostics.Process.GetProcessesByName(System.String) is helpful for getting and manipulating all the processes that are associated with the same executable file. For example, you can pass an executable file name as the processName parameter, in order to shut down all the running instances of that executable file.

Although a process P:System.Diagnostics.Process.Id is unique to a single process resource on the system, multiple processes on the local computer can be running the application specified by the processName parameter. Therefore, M:System.Diagnostics.Process.GetProcessById(System.Int32,System.String) returns one process at most, but M:System.Diagnostics.Process.GetProcessesByName(System.String) returns an array containing all the associated processes. If you need to manipulate the process using standard API calls, you can query each of these processes in turn for its identifier. You cannot access process resources through the process name alone but, once you have retrieved an array of T:System.Diagnostics.Process components that have been associated with the process resources, you can start, terminate, and otherwise manipulate the system resources.

You can use this overload to get processes on the local computer as well as on a remote computer. Use "." to specify the local computer. Another overload exists that uses the local computer by default.

You can access processes on remote computers only to view information, such as statistics, about the processes. You cannot close, terminate (using M:System.Diagnostics.Process.Kill), or start processes on remote computers.

Win98WinMe

The machineName parameter is not supported on Windows 98 or Windows Millennium Edition (Windows Me).

The following example retrieves information of the current process, processes running on the local computer, all instances of Notepad running on the local computer, and a specific process on the local computer. It then retrieves information for the same processes on a remote computer.

using System;
using System.Diagnostics;
using System.ComponentModel;

namespace MyProcessSample
{
    class MyProcess
    {
        void BindToRunningProcesses()
        {
            // Get the current process.
            Process currentProcess = Process.GetCurrentProcess();

            // Get all processes running on the local computer.
            Process[] localAll = Process.GetProcesses();

            // Get all instances of Notepad running on the local computer.
            // This will return an empty array if notepad isn't running.
            Process[] localByName = Process.GetProcessesByName("notepad");

            // Get a process on the local computer, using the process id.
            // This will throw an exception if there is no such process.
            Process localById = Process.GetProcessById(1234);


            // Get processes running on a remote computer. Note that this
            // and all the following calls will timeout and throw an exception
            // if "myComputer" and 169.0.0.0 do not exist on your local network.

            // Get all processes on a remote computer.
            Process[] remoteAll = Process.GetProcesses("myComputer");

            // Get all instances of Notepad running on the specific computer, using machine name.
            Process[] remoteByName = Process.GetProcessesByName("notepad", "myComputer");

            // Get all instances of Notepad running on the specific computer, using IP address.
            Process[] ipByName = Process.GetProcessesByName("notepad", "169.0.0.0");

            // Get a process on a remote computer, using the process id and machine name.
            Process remoteById = Process.GetProcessById(2345, "myComputer");
        }

        static void Main()
        {
            MyProcess myProcess = new MyProcess();
            myProcess.BindToRunningProcesses();
        }
    }
}

LinkDemand

for full trust for the immediate caller. This member cannot be used by partially trusted code.

SecurityPermission

to call unmanaged code. Associated enumeration: F:System.Security.Permissions.SecurityPermissionFlag.UnmanagedCode

.NET Framework
Disponible desde 1.1
Volver al principio
Mostrar: