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

Explain loosely coupled events?

1 Answers  

---

Explain what are wrapper classes?

1 Answers  

---

Explain the use of contextutil class?

1 Answers  

---

What are rcw?

1 Answers  

---

What happens when we instantiate a .NET component ?

1 Answers   DELL,

---

How to invoke .net components from com components,give the sequence ?

3 Answers   Digital GlobalSoft, UST,

---

What is durability?

1 Answers  

---

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

1 Answers  

---

How does you handle this COM components developed in other programming languages in .NET?

1 Answers  

---

Explain integrity ?

1 Answers  

---

How to make a net component talk to a com component?

1 Answers  

---

Is the com architecture same as .net architecture?

1 Answers  

---