blocks|key|1320995|text|这里有3个选项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1320996|可靠/侵入式的是，在非托管代码中设置一个钩子，每当应用程序启动时，它就会与您的C#应用程序通信。这很难正确执行，并且需要为每个进程加载一个额外的DLL。(或者，您可以设置一个驱动程序，这会更难编写)|1320997|不太可靠的方法是，定期(比如每10-30秒)列出所有进程(使用System.Diagnostics.Process类)，以查看应用程序是否启动。|offset|length|1320998|也可以从托管代码中查看Win32_Process、InstanceCreationEvent+WMI事件。我不确定这有多可靠，但我怀疑它会比轮询过程更好。|1320999|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.diagnostics.process.aspx^0|0|0|V|Q|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

you have 3 options here: 

The reliable/intrusive one, set up a hook in unmanaged code that communicates back to your C# app whenever an app is launched. This is hard to get right and involves loading an extra DLL with each process. (Alternatively you could set up a driver, which is even harder to write) 

The less reliable way, list all the processes (using the <a href="http://msdn.microsoft.com/en-us/library/system.diagnostics.process.aspx" rel="noreferrer">System.Diagnostics.Process</a> class) on a regular basis (say every 10-30 secs) to see if the app is launched. 

It also may be possible to watch the Win32_Process, InstanceCreationEvent WMI event from managed code. Not sure how reliable this is, but I suspect it would be better than polling processes.

blocks|key|1536307|text|在this+article中，您可以在服务中使用WMI+(+System.Management命名空间)来监视流程启动事件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1536308|+void+WaitForProcess()
{
++++ManagementEventWatcher+startWatch+=+new+ManagementEventWatcher(
++++++new+WqlEventQuery("SELECT+*+FROM+Win32_ProcessStartTrace"));
++++startWatch.EventArrived
++++++++++++++++++++++++%2B=+new+EventArrivedEventHandler(startWatch_EventArrived);
++++startWatch.Start();

++++ManagementEventWatcher+stopWatch+=+new+ManagementEventWatcher(
++++++new+WqlEventQuery("SELECT+*+FROM+Win32_ProcessStopTrace"));
++++stopWatch.EventArrived
++++++++++++++++++++++++%2B=+new+EventArrivedEventHandler(stopWatch_EventArrived);
++++stopWatch.Start();
}

++static+void+stopWatch_EventArrived(object+sender,+EventArrivedEventArgs+e)+{
++++stopWatch.Stop();
++++Console.WriteLine("Process+stopped:+{0}"
++++++++++++++++++++++,+e.NewEvent.Properties["ProcessName"].Value);
++}

++static+void+startWatch_EventArrived(object+sender,+EventArrivedEventArgs+e)+{
++++startWatch.Stop();
++++Console.WriteLine("Process+started:+{0}"
++++++++++++++++++++++,+e.NewEvent.Properties["ProcessName"].Value);
++}
}|code-block|syntax|javascript|1536309|WMI允许相当复杂的查询；您可以在此处修改查询，以便仅在所监视的应用程序启动时或根据其他条件触发事件处理程序。从C#的角度来看，是Here's+a+quick+introduction。|1536310|entityMap|0|LINK|mutability|MUTABLE|url|http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/46f52ad5-2f97-4ad8-b95c-9e06705428bd?wa=wsignin1.0|1|http://www.dreamincode.net/forums/showtopic42934.htm^0|U|H|1|C|0|0|0|1T|R|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@]|D|@$9|14|A|15|1|16]]|E|$]]|$1|M|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]|U|$5|P|Q|R|E|$S|V]]]]

From <a href="http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/46f52ad5-2f97-4ad8-b95c-9e06705428bd?wa=wsignin1.0" rel="noreferrer">this article</a>, you can use WMI (the <code>System.Management</code> namespace) in your service to watch for process start events.

<pre><code> void WaitForProcess()
{
 ManagementEventWatcher startWatch = new ManagementEventWatcher(
 new WqlEventQuery("SELECT * FROM Win32_ProcessStartTrace"));
 startWatch.EventArrived
 += new EventArrivedEventHandler(startWatch_EventArrived);
 startWatch.Start();

 ManagementEventWatcher stopWatch = new ManagementEventWatcher(
 new WqlEventQuery("SELECT * FROM Win32_ProcessStopTrace"));
 stopWatch.EventArrived
 += new EventArrivedEventHandler(stopWatch_EventArrived);
 stopWatch.Start();
}

 static void stopWatch_EventArrived(object sender, EventArrivedEventArgs e) {
 stopWatch.Stop();
 Console.WriteLine("Process stopped: {0}"
 , e.NewEvent.Properties["ProcessName"].Value);
 }

 static void startWatch_EventArrived(object sender, EventArrivedEventArgs e) {
 startWatch.Stop();
 Console.WriteLine("Process started: {0}"
 , e.NewEvent.Properties["ProcessName"].Value);
 }
}
</code></pre>

WMI allows for fairly sophisticated queries; you can modify the queries here to trigger your event handler only when your watched app launches, or on other criteria. <a href="http://www.dreamincode.net/forums/showtopic42934.htm" rel="noreferrer">Here's a quick introduction</a>, from a C# perspective.

blocks|key|1321132|text|监视进程是否正在运行-必须有一个服务正在运行才能做到这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1321133|如果你真的不想消耗任何资源--用普通的C编写一个简单的服务。没有MFC/ATL的服务应用程序可以消耗低至300-400kb的内存，实际上没有CPU周期。当您感兴趣的进程启动时，您可以生成您的C#服务。|1321134|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Monitor if the process is running - one service must be running to do this though.

If you really don't want to consume any ressources - write a simple service in plain C. Service application written without MFC/ATL can consume as low as 300-400 kb memory and virutally no CPU cycles. When the process you are interested in starts you can spawn your C# services.

blocks|key|1321161|text|+public+Process+IsProcessOpen(string+name)
++++++++{
++++++++++++foreach+(Process+clsProcess+in+Process.GetProcesses())
++++++++++++++++if+(clsProcess.ProcessName.Contains(name))
++++++++++++++++++++return+clsProcess;
++++++++++++return+null;
++++++++}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1321162|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code> public Process IsProcessOpen(string name)
 {
 foreach (Process clsProcess in Process.GetProcesses())
 if (clsProcess.ProcessName.Contains(name))
 return clsProcess;
 return null;
 }
</code></pre>

blocks|key|1321198|text|作为对Windows7方面不起作用的回应。如果您正在监视64位进程，那么您的进程也需要构建为在64位地址空间中工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1321199|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In reply to the Windows 7 aspect of it not working. If you are monitoring 64 bit processes your process needs to be built to work in the 64bit address space too.

I have some services that an application needs running in order for some of the app's features to work. I would like to enable the option to only start the external Windows services to initialize after the application is launched. (as opposed to having them start automatically with the machine and take up memory when the application is not needed)

I do not have access to the exe's code to implement this, so ideally I would like to write a C# .Net Windows service that would monitor when an exe is launched.

What I've found so far is the System.IO.FileSystemEventHandler. This component only handles changed, created, deleted, and renamed event types. I don't expect that a file system component would be the ideal place to find what I'm looking for, but don't know where else to go.

Maybe I'm not searching with the right keywords, but I have not yet found anything extremely helpful on Google or here on stackoverflow.com.

The solution would be required to run on XP, Vista, and Win 7 when it comes...

Thanks in advance for any pointers.

Monitor when an exe is launched

文件系统

Windows

我有一些应用程序需要运行的服务，以使应用程序的一些功能正常工作。我想启用该选项，以便在应用程序启动后仅启动外部Windows服务进行初始化。(而不是让它们自动启动机器并在不需要应用程序时占用内存)我无法访问可执行文件的代码来实现此功能，因此理想情况下，我希望编写一个C# .Net Windows服务，该服务将在可执行文...

问在启动exe时进行监视
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在启动exe时进行监视EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在启动exe时进行监视
EN