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
What is security?
What is the difference between com architecture and .net architecture?
Define object pooling?
What is durability?
Define durability?
What is com, com+ and dcom ?
What is availability?
What are loosely coupled events?
Is it true that COM objects no longer need to be registered on the server?
Explain how to register dll in com / com+ application?
What is transaction atomicity?
Why we learn the 8085? Because we are in 21 century so why we learn 8085?
how to register dll in COM / COM+ application
Explain the disadvantages of com components?
Define transaction atomicity?