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

What are loosely coupled events?

0 Answers  

---

What is use of ContextUtil class?

2 Answers  

---

Explain queued components?

1 Answers  

---

Explain role-based security?

2 Answers  

---

how to register dll in COM / COM+ application

1 Answers  

---

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

1 Answers  

---

what is the relational database of tables and forms

0 Answers   Microsoft,

---

Explain how to register com+ services?

0 Answers  

---

What is scalability?

0 Answers  

---

Explain loosely coupled events?

1 Answers  

---

What is COM?

1 Answers  

---

What is durability?

0 Answers  

---