Answer / lalan

You can no longer install COM+ DLLs into the System32 folder
on the server. In Windows 2003 server and beyond (including
Windows 7) when exporting COM+ package any DLLs registered
in Windows\System32 (or folders below that) will not be
exported. According to Microsoft Support, this is by design.
(This information has not been published publicly by
Microsoft, so we had to open a ticket with them to discover
the issue.)

The symptoms are that the exported MSI files do not contain
the COM+ DLLs if:
1. the COM+ DLL is registered in System32 and
2. the COM+ package is exported on Windows 2003 or later.
The MSI will be created and will install, however the
applications will not be able to instantiate the objects
because the DLL was never installed. Opening the MSI with a
install editor like Wise Installation Editor will reveal
that the DLL is not included in the MSI.

What is reliability?

0 Answers  

---

Explain queued components?

1 Answers  

---

What are rcw?

0 Answers  

---

Disadvantages of COM components?

2 Answers   Microsoft,

---

Explain the use of contextutil class?

0 Answers  

---

---

What is availability?

0 Answers  

---

Explain object pooling?

1 Answers  

---

Explain disadvantages of com components?

0 Answers  

---

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

3 Answers  

---

Explain loosely coupled events?

1 Answers  

---

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

1 Answers  

---

How do you make a NET component talk to a COM component?

1 Answers  

---