Jump to content

OlmanQuesada

Mobilize.Net Staff
  • Content Count

    50
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by OlmanQuesada

  1. Hello Prasad, Sorry for the late response. You can use the Profiler tool that comes in VS.NEt to determine bottlenecks and performance issues. In regards with the RecordsetHelper, this is an enhanced .NET Dataset component that emulates the classic ADO recordset used in VB6. Performance issues may be related to the querie itself, infrastructure issues of the machine where either the .NET app or the DBMS are running. Also, there's a specific feature in the RecordsetHelper may affect the performance, so I'm going to elaborate deeper on this: In VB6, when a recordset is
  2. Hi Nishant, We're escalating this as it seems to be an ongoing project. You can reach me to my email: [email protected]
  3. Hi Nishant, We've been reviewing the issue and the code snippet. Can you provide us mofre details about the file where that code snippet is located. We look for that into our framework and the migrated code of you applicaiton but we were unable to find that piece of code.
  4. Hi Nishant, Let us review this.
  5. Thanks. Could be possible to get a video of the issue coming up? We need to reproduce the issue to analyze what is causing this.
  6. Hi Nishant, Are there any additional modifilcations performed in the Mobilize Framework? Isolating the issue would be very helpful to understand what is causing the reported issue. OlmanQ
  7. Hi Nishant. Is this related to an app migrated from VB6 to WebMap? Please, send us the the version of WebMap helpers of the migrated application. Regards, OlmanQ
  8. Hi, The VB6 code needs to add the parameter to the parameter collection before accessing the value of the parameter otherwise an error at runtime is generated. The vb6 code does not indicate how the parameter at the index 0 of the collection is created, without that the followin line in the VB6 code will crash at runtime because there's no parameter at index 0. svrqAuthorise.Parameters(0) = mvlngEntityRefToMoveFrom When that code is converted to C#, a similiar situation happens, if the parameter is not created and added to the parameter collection a crash is generated. I
  9. Hi Charlie, You can solve this situation by re-migrating the code by modifying the Migration Options to use Mobilize helper classes to deal with Default Properties and Late Binding Objects, as shown in the image below. C# does not support Default Properties, so statements like cvctlAuditControl = "" in .NET will need to specify the property for the object in cvctlAuditControl to set with an empty string. The VBUC provides a mechanism to help on this: The Reflection Helper. This helper class contains a collection of .NET classes and their respective Default Property. The f
  10. Hi Aldebaran, I recommend to run the migration again and running the pre-process step before We would like you to run the migration again from scratch, making sure you have all the references right and you run the preprocess. Please make sure the ADODB reference is resolved and make sure the output folder is empty before running the migration process: Go to the "Upgrade area", right click on the project and select "Preprocess Project" option, then, when the Preprocess ends, you can upgrade the code again.
  11. Hi Aldebaran, I created a single vb6 project with a class having a similar property definition as you indicates and it doesn't compile: The vb6 compiler doesn't like having two property methods Get and Let with parameters. Do you mind if share with me (via email) the file where Duty property is defined? Also, which version of the VBUC you're using. Regards, OlmanQ
  12. Hi Romeo, If during the download process you were not prompt to register please go to the following form https://www.mobilize.net/vbuc-free-trial and then either use the download button with the email you will receive or use the file you’ll get in the email after filling-out the form. Please let me know if this works. Regards, OlmanQ
  13. Hi Astrid, In regards with the first error in Windows 7, please follow the next steps: [Workarround Steps] 1. Open a Windows command prompt with administrator privileges 2. Go the Mobilize.Net VBUC folder, where the binary files are located. It is very possible this folder is: “C:\Program Files (x86)\Mobilize.Net Visual Basic Upgrade Companion\” 3. Execute the following commands: Vbu.exe /regserver C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe ArtinSoft.VisualBasic.UpgradeExtensions.dll C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319
  14. Hello Astrid, Are you migrating the code using Windows 10 or any other windows version? Please send us an screenshots of the Solution and Resolve Reference section of the VBUC. The issue may be caused because there's a missing reference in the VB6 code (DLL with CLSID 11C67C12-105A-4F42-A5C8-CB9070F2855A). Thanks, Olman Q
  15. Hello Arnaud, The email with the license was empty without any attached file?
  16. You should recreate a new update from scratch that reflects the changes in that table. Please take a look at this URL https://stackoverflow.com/questions/34623292/how-to-update-a-table-using-join-in-visual-studio
  17. Hello, In screenshots 3 and 4, there are two issues that have to be solved manually. 1. The first is related to MSComDlg objects. In vb6 there exist only one single dialog object with several functionalities: print dialog, color dialog, open file dialog, etc. In .Net there are specific dialog objects according to their functionality. For instance, there is a openfile dialog, print dialog, etc. The VBUC tool converts every MSComDlg object into their respective equivalences in .Net, so if you find a single MSComDlg object in your VB6 form, the upgraded form in .Net would have as many .
  18. Hello Dion, Do you have a firewall that may be blocking connections attempts? You can try by implementing the winsock error event to trap error messages. My suggestion given you're now in .Net, replace the winsock by System.Net.Sockets. The communication between .Net and Interop/Activex components my be not as smoothly as expected, so using a pure .Net component could be the best option. Some guides about .Net sockets: https://docs.microsoft.com/en-us/dotnet/framework/network-programming/synchronous-client-socket-example https://docs.microsoft.com/en-us/dotnet/framewo
  19. You can find inline documentation in the helper classes and you're also free to edit them. The recordset helper tries to infer the right command type, but when the basic clauses are not fulfilled it has to get the database schema to find if the recordset is populated by querying to a table name. Retrieving the schema has a very important impact on the performance, so in this case modifying the source code by using the exec keyword would help to reduce the performance. Regards,
  20. Hello Michael, In my understanding, the recordset is populated by executing a stored-procedure. Could you provide us a quick sample of how the recordset is populated? If you use the "exec" keyword when executing stored procedures the results is the expected?
  21. Hello, ADO.Net does not provide that functionality as classic ADO or ADODB does, that’s why the VBUC generate a stub indicating that property is not supported. In order to achieve the same functionality will require changes in your migrated code. The VBUC converts classic ADO components (like the recordset) to ADO.Net components. In specific, the recordset is migrated to a helper class that inherits from the System.Data.Dataset object. This class includes methods/properties to emulate the behavior of the classic Recordset when possible, but there are some of them that ca
  22. Oracle Data provider (ODP.Net) in a migrated project Old Visual Basic 6 applications interacting with Oracle databases may rely on the MSDAORA driver in the connection string to establish such communication when that code is converted to .NET, the Visual Basic Upgrade Companion (VBUC) will keep the same connection string and therefore be use the old MSDAORA driver. But, in .NET we can take advantage of the Oracle Data Provider (ODP.Net) technology developed by Oracle instead. The following VB6 code shows a database connection though the MSDAORA provider: Dim oConn As ADODB.Conn
  23. Hi Devon, the cbo is a Activex Combobox, so it's not a .Net control. Because of that, the RowSource property cannot be assigned to a .Net class. At this point there are two alternatives: 1. Change the AxDataCombo by a .Net control. In that case it would be compatible with other .Net classes/components. This have to be done in a manual fashion as currently the VBUC does not automatically convert that control to a .Net one. 2. Migrate the vb6 code using ADODB via Com Interop (see attached file). By doing this, all classic adodb code willnot be converted to ADO.Net, so the cbo.RowS
  24. Hi, Sorry for the misunderstanding. The VBUC requires all the references to all third party components as well as any library that is part of the VB6 project . The best way to validate that is compiling the vb6 code in the same machine where the VBUC tool is installed. You can get more information about how to prepare the code to be migrated by visiting our VBUC System Requirements page https://www.mobilize.net/support/documentation/VBUC-system-requirements Please, verify the vb6 code in your machine compiles and them try converting that code. OlmanQ
×
×
  • 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