Jump to content

OlmanQuesada

Mobilize.Net Staff
  • Content count

    22
  • Joined

  • Last visited

Everything posted by OlmanQuesada

  1. VB6 to 2017 C# Migration

    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.Net code is located. If dll's required by the migrated code are not in the .Net development environment, then, missing references errors are thown by Vs.Net. 2. EWIs review: In the generated code you may find some messages inserted by the Upgrade tool that provide some useful information about code patterns/methods/events that have not a direct equivalent in .Net and require your attention: a.UPGRADE_TODO: (1065) Error handling statement (Resume Next | On Error Goto) could not be converted. b.UPGRADE_TODO: (1067) Member <member> is not defined in type <type> c.UPGRADE_ISSUE: (2064) <Object> (method | property | event) <member> was not upgraded d.UPGRADE_WARNING: (206) Untranslated statement in <method> e.UPGRADE_ERROR: (1010) The preceding line couldn't be parsed 3. If the converted application connects to a Database, some adjustments in the connection string may be needed. Please le tme know if this resolve your question. Regards, OlmanQ
  2. Migration issue from VB 6 to VB.NET 2017

    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. Please let me know if that answers your question. OlmanQ
  3. 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 oquesada@mobilize.net Regards, OlmanQ If so, it is possible for you to send me the project being migrated?
  4. 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
  5. .dvb to vb.net

    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
  6. .dvb to vb.net

    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.
  7. COM or no COM

    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 component to work in .Net, the in application must be compiled in 32 bits. If you want to have a 64bits app, yuou need to replace all COM functionality by .Net. Please let me know if you have any other question. OlmanQ
  8. MultiDimensional Array with ArraysHelper

    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
  9. MultiDimensional Array with ArraysHelper

    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
  10. MultiDimensional Array with ArraysHelper

    Hi Kevin, Could you send us a code sample where this error is happening? Please includes all variables definitions. Regards, OlmanQ
  11. rs.Properties("Unique Table")

    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
  12. rs.Properties("Unique Table")

    Hi Michael, Could be that possible to give us more context about the code. Perhaps a small VB6 sample code. Regards Olman Q
  13. license fingerprint

    Hi Marco, Let's continue with this support via email. I'll contact you at the email indicated in your profile. Olman Q
  14. license fingerprint

    Hi Marco, Thanks for the info. Our License department is asking for the license info. This cab be got from the VBUC in the menu Tools->License Info. If you can send me a screenshot that would help to track the info for that license. Regards Olman Q
  15. license fingerprint

    Hi Marco, Could you please indicate me on behalf of whom is the license. I'm asking this in order to generate a new license with the exact information. Regards
  16. VBU.exe has encountered a problem and needs to close...

    Hi Jamie, Sorry for the delay. The Helpers are written in C#, so when the code is migrated to VB.Net, the VBUC switches the "Helper Integration" option to binary, but you can change it back to "Source Code". We've found the error is not present when the code is converted to a newer version of VS.Net (like 2013/2015). Regards, Olman Q
  17. license fingerprint

    Hi Marco, I think the VBUC.Lic file may be corrupted. I'm resending to you a trial versions license to migrate up to 10K lines of code, please check your email. Please, re-install the VBUC and use the attached Trial_VBUC.Lic to activate the trial version. Regards
  18. license fingerprint

    Hi Marco, I need some additional info in order to reproduce the issue. Could you please indicate which OS are you running on? Any other useful information about how you get this error would be helpful. Another option. You can try installing and running the VBUC (using admin rights) in a fresh machine. Regards, Olman Q
  19. license fingerprint

    Hi Marco, Please make sure to run the Visual basic Upgrade Companion (VBUC) using admin rights. Can you provide us with the version number of the Visual Basic Upgrade Companion (VBUC)? You can get this by opening the VBUC and then click on the upper left arrow and select the About option. Cheers OlmanQ
  20. VBU.exe has encountered a problem and needs to close...

    Hi Jamie, Could be that possible for you to share with us additional information about variables/properties declared in this form:SGIInvoicing.frmSGIInvoicing. In addition, please try migrating the application to Visual Basic .Net by setting the "Helpers Integration" option to "Source Code" rather than "Binary". regards, OlmanQ
  21. VB6 Migration to C#(VS2015)

    Hi Rohit, In general, the VBUC try to use .Net native libraries, but there are some cases we need to use those compatibility libraries because there isn't a straightforward .Net approach. You can modify any portion of the generated code (C$ or VB.Net), including the helpers. Cheers, Olman Q
  22. VB6 Migration to C#(VS2015)

    Hi, Could you please indicate which methods you don't want to be used via the Microsoft.VisualBasic.Compatibility assembly? Regards, Olman Quesada
×