Exception management
Tech-Archive recommends: Fix windows errors by optimizing your registry
I have a serviced component that use COM interrop.
I have a problem managing exception returned by the COM object in the
component : I'm using a try/catch block to throw a new exception to the
caller. The problem is that the caller never catch this exception.
If instead I do not use a try catch block thus letting the caller manage the
exceptions directly, everything is fine. I'm probably missing something in
the serviced component but I don't know what.
TIA.
.
Relevant Pages
- Re: Serviced Component Object Pooling
... I have a serviced component exposed as SOAP endpoints via COM+ ... SOAP Services. ... > This also occurs if the serviced component throws an exception. ... the remote object is not returned back to the pool. ...
(microsoft.public.dotnet.distributed_apps) - Re: Accessing COM+
... Is the COM+ Object a serviced component created in .NET? ... marked as Serializable or an exception will be thrown. ... > I am getting an error saying that my object is not ...
(microsoft.public.dotnet.framework.aspnet.security) - Serviced Component Object Pooling
... I have a serviced component exposed as SOAP endpoints via COM+ SOAP Services. ... The exception is caught by the client as a SOAP exception, and handled ok, but the remote object is not returned back to the pool. ...
(microsoft.public.dotnet.distributed_apps) - problems running a servicedComponents using "Server" as ActivationMode
... 1- I've got a Serviced Component to add/remove/modify users from Active ... 2- When I run this component from an ASPX page in library mode I got an ... "Access Denied" exception, and this is the expected result due to the ...
(microsoft.public.dotnet.framework) - Re: Delegates and Events vs. Exception bubbling
... I agrea with letting the exception carry on to the client, ... "John Saunders" wrote: ... >> This is a serviced component that uses txns using the AutoComplete ...
(microsoft.public.dotnet.framework) |
|
