Hi, there Agreed. However, My COM+ applications are configured as Server package( running out-of-process of the application). An assembly must have strong name/and GACed (gacutil.exe /I assemblyname) in order to be a COM+ application.
It is working OK if my assemblies are not configured as COM+ application, since all *.dll and *.exe are in same directory. COM+ environment is different. Thanks Lee Tran -----Original Message----- From: Yosi Taguri [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 14, 2002 9:51 PM To: [EMAIL PROTECTED]; TRAN,Lee Subject: Re: COM+ On Tue, 13 Aug 2002 18:14:20 -0700, Lee Tr <[EMAIL PROTECTED]> wrote: >I wonder if someone could provide some pointer. >I have a couple of .Net assemblies that installed as separate COM+ >applications (A & B). I am having problems of loading an assembly >(configured as application B) from application A using Reflection. when using Reflection you always need to think of the Process that searches for the Loaded assembly. you can use fuslogvw.exe to see all the "not found" assemblies and the search path's used to find them. you need to put the dll either near the Exe running / in the path using config files. or put it in the gac using "gacutil.exr /i" ... yosi Notice: The information contained in this e-mail message and any attached files may be confidential information, and may also be the subject of legal professional privilege. If you are not the intended recipient any use, disclosure or copying of this e-mail is unauthorised. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete all copies of this transmission together with any attachments. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
