P
Pugwash
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
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