Jump to content

OlmanQuesada

Mobilize.Net Staff
  • Content Count

    50
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by OlmanQuesada

  1. Hi Good to hear that. OlmanQ
  2. Hi FGallagher, Is that possible to provide more info about the issue you are having? If would be helpful to get the following: 1. log file of the migration. You can get the log file by going to the Upgrade tab at the top of the VBUC and click on "Open Upgrade Log" button. 2. Screenshot of the error. Thanks, OlmanQ
  3. Hi, The vb6 application you're converting compiles in the machine where the VBUC is installed? OlmanQ
  4. Hi Ramya, Code migrated not necessarily compiles without requiring manual changes and having installed in the machine where the VS.Net code is located all thirdy party components required by the vb6application and are used via COM interop by the .Net migrated code. After migrating the vb6 code you may need to address the following issues in order to have the code compiling: 1. Make sure all dll's (COM and Assembly ones) and thirdy party components used by the vb6 application and used via COM Interop by the migrated code are installed on the development machine where Vs.
  5. Hi Devashi, I looks like your vb6 application is using that component/reference that is used in the migrated application as well via COM Interop. Before migrating a vb6 application, make sure the source code to be migrated compiles, that would help you to know if there are missing components/references. Some of those components can be converted to .Net equivalents but some others don't so they would be used via COM Interop. All those components that would be used via COM Interop by the migrated code will need to be properly installed in the machine where the .Net code is executed.
  6. OlmanQuesada

    Upgrade hangs

    Hi Nas, The vb6 code is compiling on the machine where it's being migrated? I think I 'll need more info about the issue. Is it possible for you to send me the project being migrated. My email is [email protected] Regards, OlmanQ If so, it is possible for you to send me the project being migrated?
  7. OlmanQuesada

    Upgrade hangs

    Hi Nas, I'd like to ask you a couple of things: 1. Version of VBUC. You can get this info in the about windows. 2. Upgrade Log file. You can get it by going to the Upgrade section, then choose Open Upgrade Log. Regards, OlmanQ
  8. Hi Shreenivas, The VBUC tool does not support dvb files as this is a proprietary AUTOCAD format so it's out of our control. Regards, OlmanQ
  9. Hi, Could you please send me a vb6 sample including that file? I tried creating a vb6 project from scratch, then adding the attached dvb file, but VB6 is not able to add that file to a valid vb6 project.
  10. Hi, The Visual Basic Upgrade Tool (VBUC for short) support the conversion of some COM/Activex components to .Net equivalents, however, it's possible some properties or methods may not be supported in .Net. At the end of the day an Activex is not a .Net component and given that VS.Net creates an interop wrapper to communicate the .Net Framework with the COM component in practice, some functionality of the Activex could cause memory-leaks. It is also possible some component design properties are not accessible in .Net. In regards with your second question, for a COM / Activex comp
  11. Thanks Kevin, I'm glad to hear the issue is gone. As you mentioned, by just modifying the property return type would fix the issue. Cheers, OlmanQ
  12. Thanks Kevin, Could you please include the definition of mobjEmployeeL2.EmployeeArray in both languages VB6 and C#, and the definition of astrGridData in vb6? OlmanQ
  13. Hi Kevin, Could you send us a code sample where this error is happening? Please includes all variables definitions. Regards, OlmanQ
  14. Hi Michael, ADO.Net does not provide a direct way to achieve that, so the migrated code should be modified to get a similar result. As the ADORecordsetHelper inherits from a Dataset, the properties of that class could be used: Given rs is a ADORecordsetHelper you can try the following: DataRow rowDel=ds.Tables["table1"].Rows[<IndexOfTheRowToDelete>]; rs.Tables["table1"].Rows.Remove(rowDel); rs.Delete() Cheers, OlmanQ
  15. Hi Michael, Could be that possible to give us more context about the code. Perhaps a small VB6 sample code. Regards Olman Q
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use