By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,041 Members | 1,046 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,041 IT Pros & Developers. It's quick & easy.

Using VB 2005 assemblies with VB 2003

P: n/a
This should be simple.

I have a VB 2003 project that needs one VB 2005 component (I cannot just
port the project as a key component is currently 2003 only).

I created a class in VB 2005, tested it and compiled to a dll. VB 2003 will
not let me reference this dll and says it is not a valid assembly. Is there
something I'm doing wrong or is this just not possible.

Thanks

Peter Smith
Mar 28 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Pugwash,

Just not possible.

Cor

"Pugwash" <pu*****@community.nospam> schreef in bericht
news:OX**************@TK2MSFTNGP11.phx.gbl...
This should be simple.

I have a VB 2003 project that needs one VB 2005 component (I cannot just
port the project as a key component is currently 2003 only).

I created a class in VB 2005, tested it and compiled to a dll. VB 2003
will not let me reference this dll and says it is not a valid assembly. Is
there something I'm doing wrong or is this just not possible.

Thanks

Peter Smith

Mar 28 '06 #2

P: n/a
It is not possible because the .NET assembly 2.0 could use something
specific to .NET 2.0, such as new class library or some new feature of the
language such as Generics. So, you can´t use 2.0 assemblies from 1.x code.
But the opposite can work, that is, port to .NET 2.0 and use an assembly
1.x. See:

Compatibility Considerations and Version Changes
http://www.gotdotnet.com/team/changeinfo/
--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com

"Pugwash" <pu*****@community.nospam> escribió en el mensaje
news:OX**************@TK2MSFTNGP11.phx.gbl...
This should be simple.

I have a VB 2003 project that needs one VB 2005 component (I cannot just
port the project as a key component is currently 2003 only).

I created a class in VB 2005, tested it and compiled to a dll. VB 2003
will not let me reference this dll and says it is not a valid assembly. Is
there something I'm doing wrong or is this just not possible.

Thanks

Peter Smith

Mar 29 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.