Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. Earlier
  3. Hi Danny Paniagua, Here is my PC configuration - Operative System: Windows 10 (Enterprise)- Language: ENU- Edition: Enterprise- Version: 1703 - OS build 15063.1029 Note: I do not see the threshold information. Hope this help. Let me know if you need any additional information. Thanks Chi
  4. DannyPaniagua

    Receive Error License is invalid when try evaluation copy

    Hi Chi, We're trying to figure out what's the problem that you are experiencing on your environment, however our tests work with no issues. We will require of your support identifying the environment characteristics that might be affecting the tool, so we will need more information about your win10 environment in order to try to reproduce the problem you have reported. We have the following configuration: - Operative System: Windows 10 - Language: ENU - Edition: Enterprise - Version: 10.0.10240 (Threshold 1) Can you provide us the information about your configuration? Thanks in advance, Danny Paniagua
  5. The purpose of this document is to provide a quick guide to implement a unit testing project with Microsoft Unit Test Framework in Visual Studio for Managed Code. It contains the basics about unit testing and provides the necessary steps to create a project, create unit tests and run them in Visual Studio Test Explorer. I hope you find it useful. Any question, comment or suggestion is welcome to make the document better. Thanks for reading. Josué. Unit_Testing.pdf
  6. Good to hear that. We will definitely look deeper into the issue to identify what was causing it. Thanks for the feedback.
  7. hi JuanManuel, I am able to make it work on Windows 7. The license is work. Is there any known issue for Windows 10? Thanks Chi
  8. Hi Chi, Let's work this together. To answer your previous question the VBUC can be installed on a Windows 10 computer, it shouldn't be an issue. I want to understand the whole process you are doing so I need a few things from your side. Setting up the VBUC license can be done through the "browse for existing license file". Select the new license you were given. After selecting the license, go to tools>license info. It should appear in here. The next thing I want to check is if you are able to apply the VBUC to a sample code. When you downloaded the VBUC it came in a .zip file. Inside of it, you will find a SampleCode.Zip. Select as the solution on the VBUC the folder (path: Sample_code>SKS>SKS_VB6) and apply the migration process. Please let me know if you still get the issue with this particular project. If you don't get any error the issue might be related to your particular project or the settings selected on upgrade options. If you still get the issue we can set up a meeting, for us to check what is causing the problem. Regards
  9. Hi JuanManuel, Is there a specific step that i need to follow for installing license? Thanks Chi
  10. hi JuanManuel, I reinstalled the software in the original PC with the latest license that you provided, received the error. Then, I installed the software in the different Windows 10 PC, and I received the same issue. Does your software support Windows 10? Thanks, Chi Below is the error from the error log. [04/26/2018 16:36:57:144] [CRASH] VBUC interrupted (Error:-2147221488) [04/26/2018 16:36:57:144] Telemetria - Migration Exception { Message: VBUC interrupted (Error:-2147221488) } [04/26/2018 16:36:57:144] ######### Error Processing project: [04/26/2018 16:36:57:144] VBUC license is invalid [04/26/2018 16:36:57:144] ErrorLength: 23 [04/26/2018 16:36:57:144] ######### [04/26/2018 16:36:57:144] Telemetria - Migration Interrupted { LOCRemaining: 30000 RAM: 2047Mb PreProcessProgress: 0 UpgradeProgress: 0 } [04/26/2018 16:36:57:145] VBMigration.MigrateVb6Project ----> MigrateVb6Project(..., ...) Return=False [04/26/2018 16:36:57:145] VBMigration.MigrateVb6Project ----> END [04/26/2018 16:36:57:145] ExecuteInternal ----> END [04/26/2018 16:36:57:145] ProcessProject ----> ExecuteInternal(...) Result=False [04/26/2018 16:36:57:152] Avoided to create an empty .sln file because the upgraded project was not found. [04/26/2018 16:36:57:152] Total elapsed time: 00:00:01 [04/26/2018 16:36:57:152] ++++++++++++++++++++++UPGRADE ENDED++++++++++++++++++++++++++++++
  11. Hi Chi, Can you please uninstall the VBUC tool and re-install it again, but use the new license as reference.
  12. Hi JuanManuel, I updated the license with your provided license. i still received the same error "UBUC license is invalid". Is there thing that i have to do beside replacing the license? I am able to view the license through the your program. It indicates the license is for 30,000 lines of code and 10,000 LOC limit per solution. The expiration date 04/24/2018 - 05/24/2018. Would you like me to resend the license that i used. Thanks Chi
  13. Hi Chi We were able to properly identify the issue, thanks for the feedback. I am sending via email the steps on how are we going to proceed. Happy Migration Regards
  14. Absolutely, here is the license that your company provided. VBUC.lic
  15. Hi Chi, Sorry for the inconvenience. We were able to identify the issue but we just need to validate it with you. Is it possible to attach the license (.lic) you were provided by email to the forum? Regards
  16. Good morning, I downloaded the evaluation copy of UBUC to try out the tool to convert my Vb6 application into VB .NET (target language is Visual Basic). Flowed the conversion steps and receive the "VBUC license is invalid" when execute the step 4 Upgrade. Here is the summary of my project 1. VB6 with 8038 lines of code 2. Run on Windows 10 OS Virtual Machine 3. Visual Studio 2015 4. Third Party tools: Sheridan 3D, FarPoint 3.0, Component One etc ... Attached is the log file and the assessment report. AssessmentWizard.exe VBUMLOGFILE.log
  17. JuanManuel

    Mobilize.Net VBUC Custom Mappings

    The following document intends to explain how the Custom Maps feature works. It was created to provide the users more control over the migration process. This feature allows the user to specify customized simple mappings. Now we can decide which elements to transform and what transformation to apply. Please feel free to ask if you have any doubts about it. Regards Mobilize.Net VBUC Custom Mappings.pdf
  18. JuanManuel

    Mobilize.Net VBUC Getting started Guide

    This document is intended for the VBUC tool created by Mobilize. The document introduces the user on how to properly setup the application, how to do your first migration process and many other cool features. The guide provides tips and recommendations but is not written in stone, we want our users to play around with the tool. Happy Migration Mobilize.Net VBUC Getting started Guide.pdf
  19. VeraBraswell

    VB6 to .NET POC

    Thank you so much for this great info!
  20. willvv

    VB6 to .NET POC

    Hello and thanks for your interest in our migration technology. There are several things that need to be done before migrating a VB6 application, including: - Completing a source dev environment. This should include all the source VB6 code and third party components. The code must compile and be debuggable, this is important both for the migration process and afterwards when you are performing manual changes to the migrated code to debug source and migrated applications side-by-side. - Defining the strategy for third party components. If there are libraries not supported by the VBUC they can either be used through COM Interop (some old components cannot be used this way), manually replaced by .NET equivalents or our team can customize the VBUC for you to automatically convert this component to another one in .NET (this is especially useful for elements used in many places). - Identifying the best set of migration options to make sure the migrated code is the best for your source VB6. This means executing the migration process a few times and comparing the results and the issues remaining in such code. - Once the code is migrated you can move it to a .NET environment as long as you have already registered any COM components that you will leave in the migrated application. Otherwise you might have problems compiling the application. This doesn't have to be a separate environment although most people prefer to do so. Our team can help you with all these steps and we even offer a quick start package that includes some on-site work with one of our migration architects to get you started without wasting any time. We can also execute part or all the project if you prefer so. Please don't hesitate to contact us at info@mobilize.net or by phone at +1.425.609.8458. Regards, - Will
  21. VeraBraswell

    VB6 to .NET POC

    What preparation or groundwork is required before a proof of concept (POC) can be conducted to convert VB6 to .NET? Is it necessary to build out a new .NET DEV environment 1st?
  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.Connection Set oConn = New ADODB.Connection oConn.ConnectionString = "Provider=MSDAORA.1;Password=" & sPassword & ";User ID = " & sUser & "; Data Source= " & sServer & ";Locales Identifier=1033" oConn.Open When this code is converted to .NET using the VBUC the code look like this: DbConnection oConn = UpgradeHelpers.DB.AdoFactoryManager.GetFactory().CreateConnection(); oConn.ConnectionString = "Provider=MSDAORA.1;Password=" + sPassword + ";User ID = " + sUser + "; Data Source= " + sServer + ";Locales Identifier=1033"; //UPGRADE_TODO: (7010) The connection string must be verified to fullfill the .NET data provider connection string requirements. More Information: https://www.mobilize.net/vbtonet/ewis/ewi7010 oConn.Open(); Note: ADODB component is migrated to ADO.NET using System.Data.Common and helper classes. As you can see the migrated application is still using the MSDAORA provider. If your final goal is taking full advantage of the .NET technology, you may want to replace that provider for the ODP.Net developed by Oracle. In this case, you need to go to the Oracle Data Provider .NET download page (http://www.oracle.com/technetwork/topics/dotnet/index-085163.html) and choose the required version of this .NET component. After installing and configuring the ODP.NET component on your machine you will have to make some minor adjustments to the migrated code: 1. Add the Oracle.DataAccess.Client factory Mobilize helper classes use a DVProviderFactory to create the right ADO.NET object according to the database connection provider in use: OleDb providers will use the System.Data.OleDb namespace. This is valid for MS-Access files and any OleDb provider like the MSDAORA one. ODBC providers will use the System.Data.ODBC namespace SqlServer can use the System.Data.SqlClient namespace Oracle providers for .NET will use Oracle.DataAccess.Client namespace that comes with the ODP.NET installer. If this assembly is not installed an exception will raise at runtime. To use the Oracle.DataAccess.Client, find the method Load DefaultFactorySettings that comes in the AdoFactoryManager class from the UpgradeHelpers.DB.Essentials helper project and uncomment-out the line: factorySection.Add("Oracle", new FactoryConfigurationElement("Oracle", "Oracle.DataAccess.Client", DatabaseType.Oracle, false)); and comment-out this line: factorySection.Add("Oracle", new FactoryConfigurationElement("Oracle", "Oracle.DataAccess.Client", DatabaseType.Oracle, false)); So, this method should looks like this: private static void LoadDefaultFactorySettings(Dictionary<string, FactoryConfigurationElement> factorySection) { factorySection.Add("Access", new FactoryConfigurationElement("Access", "System.Data.OleDb", DatabaseType.Access, true)); factorySection.Add("SQLServer", new FactoryConfigurationElement("SQLServer", "System.Data.SqlClient", DatabaseType.SQLServer, false)); //New Changes factorySection.Add("Oracle", new FactoryConfigurationElement("Oracle", "Oracle.DataAccess.Client", DatabaseType.Oracle, false)); //factorySection.Add("Oracle", new FactoryConfigurationElement("Oracle", "System.Data.OracleClient", DatabaseType.Oracle, false)); factorySection.Add("ODBC", new FactoryConfigurationElement("ODBC", "System.Data.Odbc", DatabaseType.Access, false)); } With these changes, any ADO.NET object (DBCommands, DBConnections, etc) created using the UpgradeHelpers.DB.AdoFactoryManager.GetFactory() will be instantiated using the types defined in Oracle.DataAccess.Client namespace. 2. Correct the Connection String As illustrated in the VB6 code above, the connection string is using an OLEDb provider (MSDAORA), so we need to change that string to send the parameters required by the ODP.NET provider: string conStr = "Data Source=(DESCRIPTION=(CID=GTU_APP)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST="+ sServer + ")(PORT="+ sPort + ")))(CONNECT_DATA=(SID="+ sSID + ")(SERVER=shared)))"; conStr = conStr + ";" + "User Id=" + sUser + ";Password=" + sPassword; DbConnection oConn = UpgradeHelpers.DB.AdoFactoryManager.GetFactory().CreateConnection(); oConn.ConnectionString = conStr; oConn.Open(); Basically, these are the only changes in your code to establish an Oracle DataBase connection using ODP.NET. happy migration!
  23. AlbertoEspinoza

    Upgrade From TrueDBGrid 6.0 to TrueDBGrid 7.0

    Upgrade from TDBG 6 to TDBG 7 Summary The Visual Basic Upgrade Companion supports TrueDBGrid 7.0 and later versions, but not TrueDBGrid version 6.0. To migrate code containing version 6 controls, you must first upgrade TDBG 6.0 to TDBG 7.0 Problem Description TrueDBGrid 6.0 defines some properties of the grid in the frx file, while TrueDBGrid 7.0 defines them in the frm file. When a project in Visual Basic has a form, which contains a grid of type True DB Grid 6.0, some characteristics, such as properties of columns, positions, and more are defined in the form's frx file. Since the VBUC will only take the properties defined in the frm file, those properties embedded in the frx file are not migrated. So, to solve this issue, first migrate the version 6.0 controls to version 7.0 prior to migration with VBUC. How to Upgrade to Version 7 In your VB6 development machine, install TrueDBGrid 7.0 You can get an evaluation from this link: http://download.componentone.com/pub/truedbgridpro7/eval Copy to C:\Windows\System32 the next dll: tdbg8mu.dll You can get it from this link: http://gccontent.blob.core.windows.net/gccontent/blogs/legacy/c1/2011/07/tdbg8mu1_utility.zip Register that DLL using regsvr32 Modify the file C:\Windows\vbaddin.ini adding the next line: TDBG7MU.Connect=2 In Visual Basic 6, on the menu Add-Ins/Add-in select the option "Load on startup" for "TrueDBGrid 7.0 Migration Utility" Restart Visual Basic The following button will appear on the upper menu: Upgrade from TrueDBGrid 6.0 to TrueDBGrid 7.0 and from TrueDBGrid (OLEDB) 6.0 to TrueDBGrid (OLEDB) 7.0 (if applies) Open each form and press CTRL + S to save all changes Check that each form has changed, for example: Sometimes the changes won't be applied to the forms, if that happens some workaround will be needed: Add a grid (Version 7.0) on the form Save the form Delete the grid Save again Check changes were applied to the forms Post-migration to .NET After the migration to .NET, in C# some visual elements may need correcting. For example, This is how a grid should look after the migration using version 7 of TrueDBGrid: Because the designer file loaded incompletely, this is how the grid looks after the migration (column width incorrect): The following steps can fix these kinds of problems: Modify any property of the grid, like changing the position of an element or modifying the name of the grid. These changes should be done in the code of the designer file (designer.cs) Save and close all files Re-open the form: the grid should look correct If it's necessary, don't forget to undo all changes previously applied to the designer file. This workaround is needed because sometimes the designer isn't correctly rendered in the form, so when a new change is applied, it needs to load all the designer settings. Upgrade from TDBG 6.0 to TDBG 7.0.pdf
  24. OlmanQuesada

    MSDATASRC... doesn't work in code!

    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.RowSource and the rst object may be compatible. However, as you're converting your code to .Net my suggestion would be the option 1. Regards, OlmanQ
  25. Devon

    MSDATASRC... doesn't work in code!

    This is converted code from a project. It is a basic combo box loading routine. The cbo.RowSource is an MSDATASRC an the rst is the created / converted ADORecordSetHelper. They aren't compatible! Okay so what can I assign in code to make this work?
  26. JuanManuel

    Not converting VBScript classes in Classic ASP

    Hi Nas, I would like to ask for two things. Could you provide the Log file generated and also could you provide the project/solution you are using. It'd help us find the issue. Thanks.
  27. Hi, There is only one class in the file. The file Query.asp in my previous post is complete. I have also looked in all files at classes/methods/variables named 'query' and have not found any occurrences.
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×

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