How do I distribute EnterpriseServices components as COM+ proxies?
From: Furzehill Bill (Bill_at_discussions.microsoft.com)
Date: 12/14/04
- Next message: Sam Santiago: "Re: How do I distribute EnterpriseServices components as COM+ proxies?"
- Previous message: Sam Santiago: "Re: ASP.Net Performance Problems"
- Next in thread: Sam Santiago: "Re: How do I distribute EnterpriseServices components as COM+ proxies?"
- Reply: Sam Santiago: "Re: How do I distribute EnterpriseServices components as COM+ proxies?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 14 Dec 2004 07:35:01 -0800
I have updated an old MTS based application to .Net. All seems fine on a
development machine but I have a problem with deployment. I can create
EnterpriseServices based COM+ applications on the server and export proxies.
However when any of these are installed on the client machine the application
complains that it cannot find the assembly unless I manually add it to the
Global Assembly Cache. This is not a real world option as we need the
application to be deployed automatically (via AD in this case).
Is there a way to overcome this issue? Have I missed some attribute in the
code? Or is there some option at the export time?
Any thoughts much appreciated.
- Next message: Sam Santiago: "Re: How do I distribute EnterpriseServices components as COM+ proxies?"
- Previous message: Sam Santiago: "Re: ASP.Net Performance Problems"
- Next in thread: Sam Santiago: "Re: How do I distribute EnterpriseServices components as COM+ proxies?"
- Reply: Sam Santiago: "Re: How do I distribute EnterpriseServices components as COM+ proxies?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|