|
All things migrations, software and technology
Browse by Tags
All Tags » VBUC2.0 » VBUC ( RSS)
-
|
After several months of hard work, we are proud to announce the release of version 2.2 of the Visual Basic Upgrade Companion. This version includes significant enhancements to the tool, including the ability for end users to define custom transformations, support for moving ADO. RDO and DAO to ADO.NET, additional support for third party libraries, and hundreds of bug fixes and code generation improvements based on the feedback from our clients and partners....
|
-
|
Even though the Visual Basic 6.0 runtime support files will be supported until at least 2018 in Windows Vista and Server 2008, make sure that you plan for a migration to the .NET Framework ahead of time - you don't want to hear anybody telling you "Aha. Aha!" when you have issues running the Visual Basic 6.0 IDE and find out it is no longer supported....
|
-
|
If you are running the Visual Basic Upgrade Companion for the first time, here are 5 simple steps you can follow to get you started and to get the most out of the migration from Visual Basic 6.0 to .NET....
|
-
|
In Visual Basic 6.0 you can specify optional parameters in a function or sub signature. This, however, isn't possible in .NET. In order to migrate code that uses this optional parameters, the Visual Basic Upgrade Companion creates different overload methods with all the possible combinations present in the method's signature....
|
-
|
The next version of the Visual Basic Upgrade Companion (VBUC), scheduled to be released sometime within the next month, will include a new features called Custom Maps. Custom Maps are simple translation rules that can be added to the VBUC so they are applied during the automated migration. By using Custom Maps, you can have the VBUC do more work in an automated fashion, freeing up developer's time and speeding up the migration process even more....
|
-
|
We found a very particular behavior of the TabIndex property when migrating from Visual Basic 6.0 to .NET. It is an example of a difference in behavior between VB6 and .NET for which a manual change is required....
|
-
|
A quick fix to help troubleshoot error 2869 when installing the VBUC 2.0....
|
-
|
The latest release of the Visual Basic Upgrade Companion improves the support for moving from VB6.0's On Error Statements to C# structured error handling, using try/catch blocks. In this post I will cover a couple of examples on how this transformation is performed....
|
-
|
Before starting any migration from Visual Basic 6.0 to the .NET Framework (either VB.NET or C#), we always recommend that our clients perform at least a couple of pre-migration tasks that help streamline a potential migration process: Cleaning up the VB6 codebase, and running the Code Advisor....
|
-
|
One of the new features of the Visual Basic Upgrade Companion version 2.0 is the support for Migration Profiles. These profiles give you control over which translations to use for a particular migration, improving the quality of the generated code and applying only the conversions desired (for example, for specific third party components). ...
|
-
|
The Visual Basic Upgrade Companion version 2.0 was released today! The VBUC2.0 is a considerable improvement over previous versions of the Companion....
|
|
|
|