HighTechTalks DotNet Forums  

Visual Studio COM reference

Dotnet Framework (Component Services) microsoft.public.dotnet.framework.component_services


Discuss Visual Studio COM reference in the Dotnet Framework (Component Services) forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
Olivier Matrot
 
Posts: n/a

Default Visual Studio COM reference - 04-27-2005 , 03:13 AM






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.



Reply With Quote
  #2  
Old   
Jo Siffert
 
Posts: n/a

Default Re: Visual Studio COM reference - 05-01-2005 , 01:13 PM






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:

Quote:
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.

Reply With Quote
  #3  
Old   
Olivier Matrot
 
Posts: n/a

Default Re: Visual Studio COM reference - 05-02-2005 , 02:36 AM



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...

"Jo Siffert" <jo.siffert (AT) gmx (DOT) net> wrote

Quote:
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.



Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.