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 integrity?
How to register com+ services?
Optimization technique description ?
how to register dll in COM / COM+ application
Explain how does you handle this com components developed in other programming languages in .net?
Define transaction atomicity?
Is it true that COM objects no longer need to be registered on the server?
What is the difference between com architecture and .net architecture?
What are Interop Services?
What is jit activation?
What happens when we instantiate a .NET component ?
Can .NET Framework components use the features of Component Services?
Explain the use of contextutil class?
Explain the disadvantages of com components?
Explain the new three features of com+ services, which are not there in com (mts)?
