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 happens when we instantiate a COM component ?

2 Answers   DELL,

---

can we send inputs to visual basic projects through command line arguments

1 Answers   CTS,

---

What is use of ContextUtil class?

2 Answers  

---

Explain how to register com+ services?

0 Answers  

---

What are CCW and RCW?

9 Answers   Tech Mahindra,

---

---

Define jit activation?

0 Answers  

---

Disadvantages of COM components?

2 Answers   Microsoft,

---

Define durability?

0 Answers  

---

Are com components serializable?

2 Answers   Microsoft,

---

Explain what are wrapper classes?

0 Answers  

---

Is com+ dead?

0 Answers  

---

Is it true that COM objects no longer need to be registered on the server?

0 Answers  

---