|
|
You're in the
dotnet clr
group:Object Instantiation
dotnet clr:
managed object. In the COM world, calling "New" caused the following superset of events: 1. The SCM resolves the path to the class in the registry by using its CLSID. 2. The object's class factory creates its instance in memory, and the instance's pointer is returned to the client by the SCM. 3. The client calls the IUnKnown AddRef() method on the object to increment its internal reference count. As far as I've been able to determine, the following events occur when you call "New" on a managed object: 1. The .Net runtime looks for the requested assembly by querying the GAC first, then any CodeBase entries in the .config file, and finally by probing. 2. The Garbage Collector allocates space in the managed heap for an instance of the object. 3. The runtime creates an instance of the object Questions: 1. Am I missing any steps? 2. COM objects provide class factories for instantiation. How does the .Net runtime create object instances?
Thank you!
[quoted text, click to view] >-----Original Message-----
>Hello, > >The following document should describe how assemblies are located: >http://msdn.microsoft.com/library/default.asp? url=/library/en-us/cpguide/htm >l/cpconassemblies.asp. This should provide you with information as to how >types are resolved. > >As for object instantiation, assemblies contain enough information (or >metadata) to fully describe their layout. As a result, the runtime is fully >responsible for allocating and initializing type instantiations based on >type resolution and constructor signatures. > >Because of the runtime's garbage collection mechanism, AddRef and Release >are no longer necessary in managed code (barring COM interop, of course). > >Cheers, >Simon > >-------------------- >>Content-Class: urn:content-classes:message >>From: "Hanuman" <dhaeseler@ozcap.com> >>Sender: "Hanuman" <dhaeseler@ozcap.com> >>Subject: Object Instantiation >>Date: Mon, 7 Jul 2003 06:19:54 -0700 >>Lines: 28 >>Message-ID: <0a1a01c3448a$7477a6c0$a101280a@phx.gbl> >>MIME-Version: 1.0 >>Content-Type: text/plain; >> charset="iso-8859-1" >>Content-Transfer-Encoding: 7bit >>X-Newsreader: Microsoft CDO for Windows 2000 >>Thread-Index: AcNEinR3GAGVf2WcQYWqeXtumziFZA== >>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 >>Newsgroups: microsoft.public.dotnet.framework.clr >>Path: cpmsftngxa09.phx.gbl >>Xref: cpmsftngxa09.phx.gbl microsoft.public.dotnet.framework.clr:1351 >>NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161 >>X-Tomcat-NG: microsoft.public.dotnet.framework.clr >> >>I'm trying to understand the details of calling "New" on a >>managed object. >> >>In the COM world, calling "New" caused the following >>superset of events: >>1. The SCM resolves the path to the class in the registry >>by using its CLSID. >>2. The object's class factory creates its instance in >>memory, and the instance's pointer is returned to the >>client by the SCM. >>3. The client calls the IUnKnown AddRef() method on the >>object to increment its internal reference count. >> >>As far as I've been able to determine, the following >>events occur when you call "New" on a managed object: >>1. The .Net runtime looks for the requested assembly by >>querying the GAC first, then any CodeBase entries in >>the .config file, and finally by probing. >>2. The Garbage Collector allocates space in the managed >>heap for an instance of the object. >>3. The runtime creates an instance of the object >> >>Questions: >>1. Am I missing any steps? >>2. COM objects provide class factories for instantiation. >>How does the .Net runtime create object instances? >> >>Thank you for your input! >> > > >-- > >This posting is provided "AS IS" with no warranties, and confers no rights. >Use of included script samples are subject to the terms specified at >http://www.microsoft.com/info/cpyright.htm > >Note: For the benefit of the community-at-large, all responses to this >message are best directed to the newsgroup/thread from which they >originated. > >.
Hello,
The following document should describe how assemblies are located: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm l/cpconassemblies.asp. This should provide you with information as to how types are resolved. As for object instantiation, assemblies contain enough information (or metadata) to fully describe their layout. As a result, the runtime is fully responsible for allocating and initializing type instantiations based on type resolution and constructor signatures. Because of the runtime's garbage collection mechanism, AddRef and Release are no longer necessary in managed code (barring COM interop, of course). Cheers, Simon -------------------- [quoted text, click to view] >Content-Class: urn:content-classes:message >From: "Hanuman" <dhaeseler@ozcap.com> >Sender: "Hanuman" <dhaeseler@ozcap.com> >Subject: Object Instantiation >Date: Mon, 7 Jul 2003 06:19:54 -0700 >Lines: 28 >Message-ID: <0a1a01c3448a$7477a6c0$a101280a@phx.gbl> >MIME-Version: 1.0 >Content-Type: text/plain; > charset="iso-8859-1" >Content-Transfer-Encoding: 7bit >X-Newsreader: Microsoft CDO for Windows 2000 >Thread-Index: AcNEinR3GAGVf2WcQYWqeXtumziFZA== >X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 >Newsgroups: microsoft.public.dotnet.framework.clr >Path: cpmsftngxa09.phx.gbl >Xref: cpmsftngxa09.phx.gbl microsoft.public.dotnet.framework.clr:1351 >NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161 >X-Tomcat-NG: microsoft.public.dotnet.framework.clr > >I'm trying to understand the details of calling "New" on a >managed object. > >In the COM world, calling "New" caused the following >superset of events: >1. The SCM resolves the path to the class in the registry >by using its CLSID. >2. The object's class factory creates its instance in >memory, and the instance's pointer is returned to the >client by the SCM. >3. The client calls the IUnKnown AddRef() method on the >object to increment its internal reference count. > >As far as I've been able to determine, the following >events occur when you call "New" on a managed object: >1. The .Net runtime looks for the requested assembly by >querying the GAC first, then any CodeBase entries in >the .config file, and finally by probing. >2. The Garbage Collector allocates space in the managed >heap for an instance of the object. >3. The runtime creates an instance of the object > >Questions: >1. Am I missing any steps? >2. COM objects provide class factories for instantiation. >How does the .Net runtime create object instances? > >Thank you for your input! > -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
[quoted text, click to view] > >As for object instantiation, assemblies contain enough information (or >metadata) to fully describe their layout. As a result, the runtime is fully >responsible for allocating and initializing type instantiations based on >type resolution and constructor signatures. But I've seen something different when you try to instantiate an object derived from ContextBoundObject. I used debug to monitor the process. When you call new a ContextBoundObject =============== Class A : ContextBoundObject { } A a = new A(); =============== You won't get an object of type A, you will get __TransparentProxy instead. a.GetType() is not available at the watch window, but in local variable window, you will see it's type of __TransparentProxy. But if you say: Type T = a.GetType(); in your code, use your debugger, you will see T is typeof(A). It's just weird, I am not sure how the runtime process the ContextBoundObject. Calvin
Calvin,
__TransparentProxy is an internal CLR type used for context bound and remoted objects. This type often wraps the true type. The debugger only exposes types and fields, which means that it is not smart enough to unwrap the object to show you the true type. For a *much* more detailed explanation of these internal types, please see Chris Brumme's blog entry on this subject: http://blogs.gotdotnet.com/cbrumme/PermaLink.aspx/24e9e5f5-9923-4cf9-b097-9c 018c69d5cb Cheers, Simon -------------------- [quoted text, click to view] >Content-Class: urn:content-classes:message
>From: "Calvin" <szguoxz@hotmail.com> >Sender: "Calvin" <szguoxz@hotmail.com> >References: <0a1a01c3448a$7477a6c0$a101280a@phx.gbl> <u6uG$WNRDHA.2012@cpmsftngxa09.phx.gbl> >Subject: RE: Object Instantiation >Date: Tue, 8 Jul 2003 11:58:22 -0700 >Lines: 42 >Message-ID: <03a001c34582$e718c0d0$a301280a@phx.gbl> >MIME-Version: 1.0 >Content-Type: text/plain; > charset="iso-8859-1" >Content-Transfer-Encoding: 7bit >X-Newsreader: Microsoft CDO for Windows 2000 >Thread-Index: AcNFgucY5/mGHHJbRNKj3BcEAm2YIA== >X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 >Newsgroups: microsoft.public.dotnet.framework.clr >Path: cpmsftngxa09.phx.gbl >Xref: cpmsftngxa09.phx.gbl microsoft.public.dotnet.framework.clr:1374 >NNTP-Posting-Host: TK2MSFTNGXA11 10.40.1.163 >X-Tomcat-NG: microsoft.public.dotnet.framework.clr > > >> >>As for object instantiation, assemblies contain enough >information (or >>metadata) to fully describe their layout. As a result, >the runtime is fully >>responsible for allocating and initializing type >instantiations based on >>type resolution and constructor signatures. > >But I've seen something different when you try to >instantiate an object derived from ContextBoundObject. > >I used debug to monitor the process. When you call new a >ContextBoundObject > >=============== >Class A : ContextBoundObject >{ >} > >A a = new A(); >=============== >You won't get an object of type A, you will get >__TransparentProxy instead. > >a.GetType() is not available at the watch window, but in >local variable window, you will see it's type of >__TransparentProxy. > >But if you say: > >Type T = a.GetType(); in your code, use your debugger, you >will see T is typeof(A). > >It's just weird, I am not sure how the runtime process the >ContextBoundObject. > >Calvin > > > >
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 |