|
|
You're in the
dotnet interop
group:Interop COM in C# - can't get the object released
dotnet interop:
application that will host it. I am following the COM Interop Part 1: C# Client Tutorial, Example 2, The C# Code Approach from the April 2004 MSDN library exactly. But the client will not release the COM object. The COM object is being run in its own solution and under a separate instance of Visual Studio .NET 2003. At this point the object consists only of the constructor, FinalConstruct, and FinalRelease. No methods or properties have been implemented on the interface. The C# client is the corresponding code according to the tutorial and is in the code-behind of a .NET web form. No methods or properties on the interface. However, after I have run the simple MyCOMTypeLib.MyCOMManager manager = new MyCOMTypeLib.MyCOMManager() command and have exited either the debugger or the browser independent of Visual Studio. A reference remains on MyCOM.dll. The dll cannot be rebuilt and it cannot be deleted. The only way I have found to clear the reference is to reboot the computer. Is there a way for force the DLL to be unloaded? When programming ASP, this could be done by unloading the application with the IIS manager. Better yet, why is this reference remaining contrary to documentation?
Robin,
Thank you for responding. At this point, the only operation with the COM component is to create it with 'new'. No interfaces have been called. I tried using Marshal.ReleaseCOMObject without success. Alan [quoted text, click to view] "Robin Tucker" wrote:
> How are you releasing the COM components you use (assuming MyCOMManager is a > com component)? > > If you have a reference to an interface from COM, you need to > Marshal.ReleaseCOMObject on the instance before you exit. > > "Alan" <Alan@discussions.microsoft.com> wrote in message > news:A421B104-13CF-42A2-B5F0-ECD3DF524818@microsoft.com... > >I am trying to develop an ATL COM object together with a C# web > > application that will host it. I am following the COM Interop Part 1: C# > > Client Tutorial, Example 2, The C# Code Approach from the April 2004 > > MSDN library exactly. But the client will not release the COM object. > > > > The COM object is being run in its own solution and under a separate > > instance of Visual Studio .NET 2003. At this point the object consists > > only of the constructor, FinalConstruct, and FinalRelease. No methods or > > properties have been implemented on the interface. > > > > The C# client is the corresponding code according to the tutorial and is > > in the code-behind of a .NET web form. No methods or properties on the > > interface. > > > > However, after I have run the simple > > > > MyCOMTypeLib.MyCOMManager manager = new MyCOMTypeLib.MyCOMManager() > > > > command and have exited either the debugger or the browser independent > > of Visual Studio. A reference remains on MyCOM.dll. The dll cannot be > > rebuilt and it cannot be deleted. The only way I have found to clear the > > reference is to reboot the computer. > > > > Is there a way for force the DLL to be unloaded? When programming ASP, > > this could be done by unloading the application with the IIS manager. > > > > Better yet, why is this reference remaining contrary to documentation? > > > > > > > > > >
Robin,
At this point the COM object does nothing. It doesn't even have variables ore interface members yet. Before developing it, I want to make sure I know how to do the interop correctly, starting from creating and releasing it. Actually, I think that the problem is in ASPNET. I am using a web application to develop and debug the COM object. When using ASP, one simply unloads the application after each debugging run. I don't know how to unload ASPNET other than to stop and restart w3svc. Alan [quoted text, click to view] "Robin Tucker" wrote:
> Well, in my experience there is something else to consider. Firstly, if the > COM object is "out of process", it will stay in memory unless it is > explicitly "exited". I know this only from using Microsoft Word interop, > where even if you release all references to the COM object, the image stays > in task manager, so you execute the m_WordApplication.Quit command and it > goes. Perhaps you are out of process and hence also need to implement a > quit command on your object? > > "Alan" <Alan@discussions.microsoft.com> wrote in message > news:95108CE0-1C84-46B4-BD9E-7B047CC0CF73@microsoft.com... > > Robin, > > > > Thank you for responding. > > > > At this point, the only operation with the COM component is to create it > > with 'new'. No interfaces have been called. I tried using > > Marshal.ReleaseCOMObject without success. > > > > Alan > > > > > > "Robin Tucker" wrote: > > > >> How are you releasing the COM components you use (assuming MyCOMManager > >> is a > >> com component)? > >> > >> If you have a reference to an interface from COM, you need to > >> Marshal.ReleaseCOMObject on the instance before you exit. > >> > >> "Alan" <Alan@discussions.microsoft.com> wrote in message > >> news:A421B104-13CF-42A2-B5F0-ECD3DF524818@microsoft.com... > >> >I am trying to develop an ATL COM object together with a C# web > >> > application that will host it. I am following the COM Interop Part 1: > >> > C# > >> > Client Tutorial, Example 2, The C# Code Approach from the April 2004 > >> > MSDN library exactly. But the client will not release the COM object. > >> > > >> > The COM object is being run in its own solution and under a separate > >> > instance of Visual Studio .NET 2003. At this point the object consists > >> > only of the constructor, FinalConstruct, and FinalRelease. No methods > >> > or > >> > properties have been implemented on the interface. > >> > > >> > The C# client is the corresponding code according to the tutorial and > >> > is > >> > in the code-behind of a .NET web form. No methods or properties on the > >> > interface. > >> > > >> > However, after I have run the simple > >> > > >> > MyCOMTypeLib.MyCOMManager manager = new MyCOMTypeLib.MyCOMManager() > >> > > >> > command and have exited either the debugger or the browser independent > >> > of Visual Studio. A reference remains on MyCOM.dll. The dll cannot be > >> > rebuilt and it cannot be deleted. The only way I have found to clear > >> > the > >> > reference is to reboot the computer. > >> > > >> > Is there a way for force the DLL to be unloaded? When programming ASP, > >> > this could be done by unloading the application with the IIS manager. > >> > > >> > Better yet, why is this reference remaining contrary to documentation? > >> > > >> > > >> > > >> > > >> > >> > >> > >
How are you releasing the COM components you use (assuming MyCOMManager is a
com component)? If you have a reference to an interface from COM, you need to Marshal.ReleaseCOMObject on the instance before you exit. [quoted text, click to view] "Alan" <Alan@discussions.microsoft.com> wrote in message news:A421B104-13CF-42A2-B5F0-ECD3DF524818@microsoft.com... >I am trying to develop an ATL COM object together with a C# web > application that will host it. I am following the COM Interop Part 1: C# > Client Tutorial, Example 2, The C# Code Approach from the April 2004 > MSDN library exactly. But the client will not release the COM object. > > The COM object is being run in its own solution and under a separate > instance of Visual Studio .NET 2003. At this point the object consists > only of the constructor, FinalConstruct, and FinalRelease. No methods or > properties have been implemented on the interface. > > The C# client is the corresponding code according to the tutorial and is > in the code-behind of a .NET web form. No methods or properties on the > interface. > > However, after I have run the simple > > MyCOMTypeLib.MyCOMManager manager = new MyCOMTypeLib.MyCOMManager() > > command and have exited either the debugger or the browser independent > of Visual Studio. A reference remains on MyCOM.dll. The dll cannot be > rebuilt and it cannot be deleted. The only way I have found to clear the > reference is to reboot the computer. > > Is there a way for force the DLL to be unloaded? When programming ASP, > this could be done by unloading the application with the IIS manager. > > Better yet, why is this reference remaining contrary to documentation? > > > >
Well, in my experience there is something else to consider. Firstly, if the
COM object is "out of process", it will stay in memory unless it is explicitly "exited". I know this only from using Microsoft Word interop, where even if you release all references to the COM object, the image stays in task manager, so you execute the m_WordApplication.Quit command and it goes. Perhaps you are out of process and hence also need to implement a quit command on your object? [quoted text, click to view] "Alan" <Alan@discussions.microsoft.com> wrote in message news:95108CE0-1C84-46B4-BD9E-7B047CC0CF73@microsoft.com... > Robin, > > Thank you for responding. > > At this point, the only operation with the COM component is to create it > with 'new'. No interfaces have been called. I tried using > Marshal.ReleaseCOMObject without success. > > Alan > > > "Robin Tucker" wrote: > >> How are you releasing the COM components you use (assuming MyCOMManager >> is a >> com component)? >> >> If you have a reference to an interface from COM, you need to >> Marshal.ReleaseCOMObject on the instance before you exit. >> >> "Alan" <Alan@discussions.microsoft.com> wrote in message >> news:A421B104-13CF-42A2-B5F0-ECD3DF524818@microsoft.com... >> >I am trying to develop an ATL COM object together with a C# web >> > application that will host it. I am following the COM Interop Part 1: >> > C# >> > Client Tutorial, Example 2, The C# Code Approach from the April 2004 >> > MSDN library exactly. But the client will not release the COM object. >> > >> > The COM object is being run in its own solution and under a separate >> > instance of Visual Studio .NET 2003. At this point the object consists >> > only of the constructor, FinalConstruct, and FinalRelease. No methods >> > or >> > properties have been implemented on the interface. >> > >> > The C# client is the corresponding code according to the tutorial and >> > is >> > in the code-behind of a .NET web form. No methods or properties on the >> > interface. >> > >> > However, after I have run the simple >> > >> > MyCOMTypeLib.MyCOMManager manager = new MyCOMTypeLib.MyCOMManager() >> > >> > command and have exited either the debugger or the browser independent >> > of Visual Studio. A reference remains on MyCOM.dll. The dll cannot be >> > rebuilt and it cannot be deleted. The only way I have found to clear >> > the >> > reference is to reboot the computer. >> > >> > Is there a way for force the DLL to be unloaded? When programming ASP, >> > this could be done by unloading the application with the IIS manager. >> > >> > Better yet, why is this reference remaining contrary to documentation? >> > >> > >> > >> > >> >> >>
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |