Ok I've now understood that I must use the .NET tab, instead of COM tab.
I solved my problems as you suggested. On the developpement machine, add a
reference with a file located somewhere on disk. On the production machine,
the DLL is only placed in the GAC. And in visual studio, "Copy Local" on a
reference is set to false. This helps reduce DLL hell...
[quoted text, click to view] "Jo Siffert" <jo.siffert@gmx.net> wrote in message
news:%23fwsFEnTFHA.2172@tk2msftngp13.phx.gbl...
> Hi,
>
> use the .Net-Tab and browse for the DLL containing your SCs.
> If you only have a copy of the DLL in the gac, use cmd.exe to navigate to
> c:\windows\assembly\gac\.....\your_sc.dll, copy the dll to some different
> directory and add a reference to it.
>
> Can you give more details about your assembly loading problems on your
> production machine?
>
> /Jo
>
> Olivier Matrot wrote:
>
>> Using Visual Studio 2003, you reference a service component with a
>> project reference. This is easy ans straightforward. BUT, How can I
>> reference a component that is installed in the system (I do not have the
>> project). If I add a COM reference, the following message appears : "A
>> reference to 'xxxxx' could not be added. Converting the type library to a
>> .NET assembly failed. Type library xxxxxxx was exported from a CLR
>> aseembly and can not be re-imported as a CMLR assembly".
>>
>> Next, what about the deployment scenario on production machines. I
>> encounter assembly loading failures that I do not understand.