Answer Posted / virat sarswat
Correcting Rajeev's answer
COM vs .NET Component
.NET Component=Object based communication
COM=Interface based communication
.NET Component=Garbage Collector to manage memory
COM=Reference count will be used to manage memory
.NET Component=Type Standard objects
COM=Binary Standard objects
.NET Component=Objects are created by normal new operator
COM=Objects are created by coCreateInstance
.NET Component=Exceptions will be returned
COM=HRESULT will be returned
.NET Component=Object info resides in assembly files
COM=Object info resides in Type library
| Is This Answer Correct ? | 23 Yes | 5 No |
Post New Answer View All Answers
Define object pooling?
What are loosely coupled events?
What is transaction atomicity?
Is it true that COM objects no longer need to be registered on the server?
Is com+ dead?
What is jit activation?
What is ccw?
Explain the disadvantages of com components?
What is security?
Explain how to register com+ services?
What is integrity?
What is availability?
How CCW and RCW is working?
Define jit activation?
Explain the new three features of com+ services, which are not there in com (mts)?
