• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 439
  • Last Modified:

Reference an assembly in visual studio 2003 that was created in visual studio 2005

Hello,
   I have an assembly that I created in Visual Studio 2005.  It is created in the directory c:\logging\bin\Release\logging.dll.  I wish to use this assembly in visual studio 2003.  When I try to add a reference to it I browse to it, select the file and then get "A referenct to 'c:\logging\bin\Release\logging.dll' could not be added.  This is not a valid assembly or COM component.  Only assemblies with extension 'dll' and COM components can be referenced.  Please make sure that the file is accessible, and that it is a valid assembly or COM component"  In other VS 2005 solutions I have added the "Logging" project and then set a project reference.  Obviously with 2003 that is a problem.  Any suggestions would be greatly appreciated.

Thanks
0
wildrobo
Asked:
wildrobo
  • 2
  • 2
1 Solution
 
Éric MoreauSenior .Net ConsultantCommented:
Hi wildrobo,

I never a way. I even saw someone trying to use COM to use the 2005 dll without success.

Cheers!
0
 
LordWabbitCommented:
Copy the code out and put it into a vs2003 project, fix where needed and then rebuild.
0
 
wildroboAuthor Commented:
I do appreciate that, but the purpose I built the component for was not to have to maintain different code bases.  I guess if that is the only way to do it, I should create it in VS2003 because it would be compatible with 2005 then right?
0
 
LordWabbitCommented:
Correct, not sure why they couldn't get the compatability to run both ways, some sort of dotnet wrapper or something, but 2005 can use 2003 but 2003 cant use 2005 (type thing).  Perhaps they will release a service pack later to sort it out.  Although to be honest by the time they do that most ppl will be used to working around the problem.
0
 
Éric MoreauSenior .Net ConsultantCommented:
>>I should create it in VS2003 because it would be compatible with 2005 then right?

Yes. It is very stupid not to be able to use vs2005 from vs2003. It stops us doing incremental upgrades.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now