Try asking in the C# forum instead of the COM forum. Christian Graus - Microsoft MVP - C++

And what do you mean by an "enter Form". It's rather ambiquous, and serialization doesn't really care what kind of object you're serializing so long as its attributed directly with SerializableAttribute. That attribute is not inheritted. Since the Form class is not attributed with SerializableAttribute, then you need to attribute your derivative class. But ask yourself why you need to serialize it and what, specifically, you need to serialize. Much of the form is specific to that instance and should not be serialized (like the Handle) if you plan on either re-creating it or saving it across multiple sessions (a session being separate logins, processes, etc.). To control how your form (or any object) is serialized, implement ISerializable. For more information on serialization, read Serializing Objects[^] in the .NET Framework SDK online. The SDK is also installed by default with VS.NET and can be installed stand-alone from http://msdn.microsoft.com/netframework[^]. This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Sustained Engineering Microsoft [My Articles] [My Blog]

1.Firstly, DoubleClick event should fire, without any doubt. I do not find any problem in it. 2.Click or DoubleClick Event Handler of the DataGrid or other Controls has EventArg argument, you would not be getting the colum number / row number information from the EventArg. You should use either MouseDown or MouseUp event Handler which has MouseEventArgs in the arguments. MouseDown Event and HitTest method will get you the desired. Refer the below link for details. DataGrid HitTest Method[^]

Wail A.Salem wrote: how we can prevent the user from ending the process from the task manager? You can't. But you can respond to notification that a user is killing your process. Handle the Closing or Close event of your main form (the one you pass directly or indirectly to Application.Run). If your code is not finished in a timely manner, your process will be killed. There are a few other ways as well, but I'll leave this as an exercise for you. I recommend reading through the Windows Management APIs section of the MSDN Online Library[^]. As for the second question, you have to write this to the registry yourself. So add a registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\<YourServiceName>\Type such as 288 (256 for "Interact with desktop" OR'd with 32 for the service type), or whatever is appropriate for your service type so long as you perform a bitwise OR with 256 and run it as the LocalSystem (default). If you run it as a user, then the service can only interact with that user's desktop (assuming the user has an associated desktop session and can log in locally). Microsoft MVP, Visual C# My Articles

What was wrong with the responses that Michael and I gave you the other day? No one is going to do this work for you. - Nick Parker My Blog | My Articles

Nick Parker wrote: however I took into consideration that he was a student and learning the process behind P/Invoke would be helpful in the long run. Certainly. However, speaking from experience. TAPI can be hard enough to get to work, without having the extra overhead of learning P/Invoke too. Michael CP Blog [^]