Accessing .NET Assemblies from COM+ Component
-
I have created a COM+ component using C# (System.EnterpriseServices.ServicedComponent). I will register the component with Component Services, however, the component uses other .NET assemblies. What is the best way to access thos assemblies from my serviced component? I don't want to register them in the GAC since they are not shared assemblies. Any suggestions? Thanks. -Matt ------------------------------------------ The 3 great virtues of a programmer: Laziness, Impatience, and Hubris. --Larry Wall
-
I have created a COM+ component using C# (System.EnterpriseServices.ServicedComponent). I will register the component with Component Services, however, the component uses other .NET assemblies. What is the best way to access thos assemblies from my serviced component? I don't want to register them in the GAC since they are not shared assemblies. Any suggestions? Thanks. -Matt ------------------------------------------ The 3 great virtues of a programmer: Laziness, Impatience, and Hubris. --Larry Wall
Is your component going to be deployed as a library application or a server application? If its going to be deployed as a library app then you can just dump the appropriate files into the client applications along with the serviced component assembly. If you are deploying your component as a server applicaiton you should put it in the GAC. This is done to allow the COM+ to load the assembly independent of the directory in which the actual client is running, and also to allow more than one client to use the same assembly. This posting is provided "AS IS" with no warranties, and confers no rights. Alex Korchemniy
-
Is your component going to be deployed as a library application or a server application? If its going to be deployed as a library app then you can just dump the appropriate files into the client applications along with the serviced component assembly. If you are deploying your component as a server applicaiton you should put it in the GAC. This is done to allow the COM+ to load the assembly independent of the directory in which the actual client is running, and also to allow more than one client to use the same assembly. This posting is provided "AS IS" with no warranties, and confers no rights. Alex Korchemniy
Thanks for your help. I really appreciate it. Will my COM+ component look for the DLLs in the system path? Or is the GAC the only solution if I'm deploying it as a server app? I've just had problems before when I've put component in the GAC and I'm trying to avoid that. Thanks. -Matt ------------------------------------------ The 3 great virtues of a programmer: Laziness, Impatience, and Hubris. --Larry Wall
-
Thanks for your help. I really appreciate it. Will my COM+ component look for the DLLs in the system path? Or is the GAC the only solution if I'm deploying it as a server app? I've just had problems before when I've put component in the GAC and I'm trying to avoid that. Thanks. -Matt ------------------------------------------ The 3 great virtues of a programmer: Laziness, Impatience, and Hubris. --Larry Wall
This is a helpful link: How the Runtime Locates Assemblies[^] This posting is provided "AS IS" with no warranties, and confers no rights. Alex Korchemniy