Answer Posted / 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.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
Optimization technique description ?
Explain the new three features of com+ services, which are not there in com (mts)?
What is reliability?
Explain disadvantages of com components?
Is com+ dead?
Explain the disadvantages of com components?
What is the difference between com architecture and .net architecture?
Define jit activation?
Explain how to register dll in com / com+ application?
What happens when we instantiate a .NET component ?
What is manageability?
Explain how does you handle this com components developed in other programming languages in .net?
What is transaction atomicity?
What is jit activation?
How CCW and RCW is working?
