Groups | Blog | Home
all groups > dotnet component services > august 2004 >

dotnet component services : Strange Debugging Experience With a ServicedComponent



Raghu
8/18/2004 3:45:03 PM
I have a component that subclasses ServicedComponent. It has both JITA and
object pooling enabled. So all initialization code in in Activate method. It
is deployed as a com+ server application. When calling it from a test
application, it creates the object successfully. When keep a break point in
Activate method, the data members are not initliazing properly. When I step
over the code line that assigns a constant variable value to a data member,
the data member still contians null value. However I could set the value of
data member in the local/watch window. What is reason behind this? The os is
windows 2003 with VS.NET 2003. There is no out sync problem with pdb file or
any thing.

When I tried to deploy it as com+ library application, the same behavior
persisted. When I removed all ServicedComponent related code and moved init
code from Activate method to public constructor, every thing worked as
expected.

Thanks.
Raghu/..

Raghu
8/20/2004 6:35:06 AM
Figured out that VS.NET can not show values of a servied component because
it works with transparent proxy to the actual object. Even though member
variables are showing as null, they actually contained right values.

[quoted text, click to view]

AddThis Social Bookmark Button