D
dimpant
Guest
Hello,
I've managed to migrate an application from VB4 to VB.NET using the wizard of the Visual Basic 2008 Express Edition. The migration took place in a Windows XP Virtual Machine where VB4, VB6 and VB 2008 Express Edition are installed. The migration path was VB4->VB6->VB 2008 Express Edition.
The wizard retained components such as the MSGrid by adding COM references:
1. Microsoft DAO 2.5/3.51 Compatibility Library COM version 3.5.0.0 (Path = [..]\Interop.DAO.dll)
2. Microsoft Grid Control COM version 1.0.0.0 (Path = [...]\AxInterop.MSGrid.dll)
3. Sheridan 3d Controls COM version 1.0.0.0 (Path = [...]\AxInterop.Threed.dll)
The problem is that I cannot build the VB.NET project with Visual Studio 2019 in Windows 10. At first, all three references (AxMSGrid, AxThreed, DAO) were shown with a yellow warning icon in solution explorer. The icon disappeared for AxMSGrid and AxThreed after I registered GRID32.OCX and THREED32.OCX (using regsvr32) but I still get the following errors when I build the project:
"Could not resolve COM reference a8b3b723-0b5a-101b-b22e-00aa0037b2fc version 1.0. Object reference not set to an instance of an object."
"Could not resolve COM reference 0ba686c6-f7d3-101a-993e-0000c0ef6f5e version 1.0. Object reference not set to an instance of an object."
As far as I can tell, both those GUIDs refer to AxMSGrid and AxThreed while as I said, those references look OK in the solution explorer.
So, I don't quite understand what the problem really is and what to do next. Of course, I algo get a warning (not an error) about the DAO reference which I don't why it's even used since there is no database used in the application whatsoever.
How can I have the project built in VS 2019 on Windows 10?
any ideas?
dimpant
Continue reading...
I've managed to migrate an application from VB4 to VB.NET using the wizard of the Visual Basic 2008 Express Edition. The migration took place in a Windows XP Virtual Machine where VB4, VB6 and VB 2008 Express Edition are installed. The migration path was VB4->VB6->VB 2008 Express Edition.
The wizard retained components such as the MSGrid by adding COM references:
1. Microsoft DAO 2.5/3.51 Compatibility Library COM version 3.5.0.0 (Path = [..]\Interop.DAO.dll)
2. Microsoft Grid Control COM version 1.0.0.0 (Path = [...]\AxInterop.MSGrid.dll)
3. Sheridan 3d Controls COM version 1.0.0.0 (Path = [...]\AxInterop.Threed.dll)
The problem is that I cannot build the VB.NET project with Visual Studio 2019 in Windows 10. At first, all three references (AxMSGrid, AxThreed, DAO) were shown with a yellow warning icon in solution explorer. The icon disappeared for AxMSGrid and AxThreed after I registered GRID32.OCX and THREED32.OCX (using regsvr32) but I still get the following errors when I build the project:
"Could not resolve COM reference a8b3b723-0b5a-101b-b22e-00aa0037b2fc version 1.0. Object reference not set to an instance of an object."
"Could not resolve COM reference 0ba686c6-f7d3-101a-993e-0000c0ef6f5e version 1.0. Object reference not set to an instance of an object."
As far as I can tell, both those GUIDs refer to AxMSGrid and AxThreed while as I said, those references look OK in the solution explorer.
So, I don't quite understand what the problem really is and what to do next. Of course, I algo get a warning (not an error) about the DAO reference which I don't why it's even used since there is no database used in the application whatsoever.
How can I have the project built in VS 2019 on Windows 10?
any ideas?
dimpant
Continue reading...