Your best bet is to look into Windows Shell documentation and find out which Win32 calls (or possibly, Registry keys) can retrieve the list of Windows context menu options. That's the easy part. From there, you're gonna have to hook up your application to interop with the Windows shell; so that if you right click on some object in your program, it will allow you to, say, copy the file or text to the clipboard. That will be difficult. I recommend you look for other options. What is it you want to do?

I couldn't seem to get that to work. However, I did find another solution. I found a class that receives all mouse and keyboard events from the system. I hooked up a couple events and now my program is told when someone clicks the mouse or presses a key. Then I just GetForeGroundWindow to get the active window and change the IntPtr my program is using to know what has focus. Works great!

that is my hope.

Doh! I had my collection inside my Task class setup as an XMLAttribute. I removed the syntax and it worked.

This morning I created a simple remotable object with a delegate and event using that delgate. On the server side where I created the object, I setup an eventhandler for the event I created and marshaled the object. On the client side when I get a reference to the object using Activator.GetObject and I try creating an eventHandler for the same event, I get a security policy error. I was hoping that setting up an eventhandler on the object on both server and client sides that it would be a way that I could communicate back and forth between the server and client. I know that this is probably a misguided attempt at client/server and server/client communication, but I'm new to this. Can anyone point me in the right direction?

There are 2 ways I would go about this: The graceful way would be to use remoting. In your code that checks for a single instance you would set up remoting to communicate with the running instance of your program and call a method in that instance to bring itself to the foreground. Remoting is ideal for communicating locally across application and process boundaries. The only drawback is that you need a network card to avoid problems. In the case that you can't guarantee your client's will have a NIC you can use Windows API. You need to call the Activate Window API. Here's a quick intro into that API. http://www.devhood.com/tutorials/tutorial_details.aspx?tutorial_id=711

That should be: FieldInfo field this.GetType().GetField(name, BindingFlags.Public | BindingFlags.NonPublic | BindingFlags.Instance); This will include non-public (i.e., private or protected) members in the search as well. Microsoft MVP, Visual C# My Articles