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

   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.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

Copy the code out and put it into a vs2003 project, fix where needed and then rebuild.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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?
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.
É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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.