From .Net 2003 to VS2005

Our project has got some user controls in the old VB6 Version, in the form of .ocx. When upgrade to VB.net 2003, they were changed to interop&Axinterop dlls. Now I hope to open the project in VS2005, and i've done upgrade following the upgrade guidance.

But after upgrading, there were some warnings said the reference to those dlls can not be found.

I checked the vbproj file of VS2003 and found out that in <reference> node, there're "name" and "assemblyname" properties. When they're the same, the reference in VS2005 is no problem. Otherwise, the refernce cannot be found. I'm really confused about this, anyone can help me? Thank you very much.

[703 byte] By [rosyou] at [2008-2-18]
# 1
I would suggest removing those references and re-adding a reference to the original .ocx control - that may fix it.
AlexMoura at 2007-8-31 > top of Msdn Tech,Visual Basic,Visual Basic Interop and Upgrade...
# 2

Thanks, it really helps.

But here's another question:

When I add AxtiveX control Reference in VS2005, it should generate 2 dlls named xxxx.dll & AXxxxx.dll.

But I only got the first of them. It seems that when reference is added, the Aximp.exe didn't run.

Is there any settings about it?

Thanks again!

rosyou at 2007-8-31 > top of Msdn Tech,Visual Basic,Visual Basic Interop and Upgrade...
# 3

Hi -

I'd only expect that you see one DLL for each OCX that you reference. In VS2005, the default behavior is to create a DLL called Interop.xxxx.dll with a friendly Reference name of xxxx. If you double click on the reference, you should see the Interop.xxxx namespace in Object browser. If the above is true then the equivalent of aximp.exe is working fine. Could you please verify?

If not, could you please tell us what OCX you're referencing, and the specific steps you're trying, and details about the problem?

thanks,

Paul

PaulYuk_MS at 2007-8-31 > top of Msdn Tech,Visual Basic,Visual Basic Interop and Upgrade...