vb6-migration

I should convert a huge load of code which was written in VBA (Excel) to VB6. But I really do not know what I have to take care of or where to begin. Therefore it would be great to get some hints here from the VB6 experts. I installed already MS Visual Studio and played a bit around. But I'm not a VB6 expert and do not really know what I have to do. The final goal is to have all the VBA code, which is currently placed in one excel vba macro into a VB6 project and create a .dll out of it. This .dll should be referenced by the excel and the excel should run like it does now :-) For example what

The following VB6 code connects to some third party software and forces a login with the admin username and password: Set obj = GetObject(, "workspace.application") obj.System.FixLogin strAdminUsername, strAdminPassword I am wanting to do the same task in C# but as a very green C# developer (about 3 months experience) I have no idea how to do this. I've spent a very frustrating day on Google but have found nothing that fits the bill (most of it I couldn't even understand) I know even less about VB6 than I do about C#, but VB6 makes it look so easy. Also I can't test connecting to this third

I am currently exploring the option of porting some older VB6 application to WPF with C#. The plan, in phase one, is to port several key forms and not all the application. The theoretical goal is to open the VB6 form in a container of some sort within WPF via an ActiveX dll. Is this even possible? I've tried looking at the Interop and can't seem to find a solid example of how get it to work with anything but Win32 controls, not a full form. I have full access to the old VB6 code and can modify it in anyway needed. The following screenshot of the main WPF app would serve as the wrapper

I know that there are already Questions about VB6 migration, but the code base of my project brings some new questions here. I have to say the Code quality, structure and architecture is just a nightmare. There are 2 Big Projects: Nr.1 with 40 Forms, 40 Modules and a few class files, this EXE is kind of a "base system". Nr.2 with 80 Forms, 20 Modules and a few class files again, this EXE calls functions form the "base system". Then there are ~10 other Projects with GUI (1-3 Forms each) and another 90 non-GUI Projects, most of them EXE Files, some DLLs. The DLLs are written in C, C++ and VB6.

Are control arrays supported in .Net? We are talking about converting a legacy app from VB6 to .Net. The app has a lot of control arrays. I've read different articles that differ if .Net supports control arrays. Can anyone give me a definitive answer if .Net supports control arrays like VB6 does? Is this for the latest version of .Net 4.0? Or is there a version limitation? Also, if this is possible is it a straight conversion? If not what flaming hoops would one have to jump through to make this happen? Thank You! A "straight conversion" is not possible, but you can create control arrays in a

Given that the Visual Basic 6.0 runtime ships with Windows 7 and will continue to be supported for the lifetime of the OS ( until January 2020 ) and that the Visual Basic 6.0 IDE, though no longer supported , is fairly stable, what are the risks around keeping mission-critical applications in Visual Basic 6.0 for the next several years? MarkJ The official advice for owners of VB6 apps from Microsoft UK is: [Do not upgrade or replace your VB6 application if] your application is working great, it has not required any changes for many years, there are no plans to extend the functionality, nor a