Unless there's something specific to VS2003, that has either been upgraded to something else or descarded otherwise in VS2005, that your VS2003 dll is making use of, this problem shouldnt occur.
What work was your VS2003 dll performing. Is there anything specific to VS2003 you can think of that your dll was making use of.
Regards
Ankur Verma
|