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 .NET component ?

0 Answers   DELL,

---

How CCW and RCW is working?

0 Answers  

---

Explain durability?

1 Answers  

---

Explain integrity ?

1 Answers  

---

How will you register com+ services?

3 Answers  

---

Explain object pooling?

1 Answers  

---

Explain how does you handle this com components developed in other programming languages in .net?

0 Answers  

---

What is the difference between com architecture and .net architecture?

0 Answers  

---

Difference between COM and .NET component ?

2 Answers   DELL,

---

Define jit activation?

0 Answers  

---

Explain JIT activation?

3 Answers  

---

Is the COM architecture same as .Net architecture? What is the difference between them?

1 Answers  

---