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

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

how to register dll in COM / COM+ application

1 Answers  

---

WHY WE LEARN THE 8085 ? BECAUSE WE R IN 21 CENTURI SO WHY WE LEARN 8085?

2 Answers  

---

Are com components serializable?

2 Answers   Microsoft,

---

Difference between .NET components and COM components?

3 Answers   Microsoft,

---

Define transaction atomicity?

0 Answers  

---

What is availability?

0 Answers  

---

Which namespace do the classes, allowing you to support COM functionality, are located?

1 Answers  

---

What is COM?

1 Answers  

---

Explain JIT activation?

3 Answers  

---

What is Pinvoke?

0 Answers  

---

Is com+ dead?

0 Answers  

---

Explain the new three features of com+ services, which are not there in com (mts)?

0 Answers  

---