Difference between COM and .NET component ?
Answers were Sorted based on User's Feedback
Answer / 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 |
Answer / rajeev
COM vs .NET Component
COM=Object based communication
.NET Component=Interface based communication
COM=Garbage Collector to manage memory
.NET Component=Reference count will be used to manage memory
COM=Type Standard objects
.NET Component=Binary Standard objects
COM=Objects are created by normal new operator
.NET Component=Objects are created by coCreateInstance
COM=Exceptions will be returned
.NET Component=HRESULT will be returned
COM=Object info resides in assembly files
.NET Component=Object info resides in Type library
Is This Answer Correct ? | 7 Yes | 21 No |
What is the new three features of COM+ services, which are not there in COM (MTS) ?
can we send inputs to visual basic projects through command line arguments
Explain durability?
Define manageability?
Explain queued components?
Define object pooling?
Difference between COM and .NET component ?
How to make a net component talk to a com component?
What is the new three features of COM+ services, which are not there in COM (MTS)
Explain how does you handle this com components developed in other programming languages in .net?
Can .NET Framework components use the features of Component Services?
WHY WE LEARN THE 8085 ? BECAUSE WE R IN 21 CENTURI SO WHY WE LEARN 8085?