|
All things migrations, software and technology
Browse by Tags
All Tags » Visual Basic to C# ( RSS)
-
|
One very common requirement for migration projects is to adapt certain error handling patterns used in a customer’s Visual Basic 6.0 code to the structured error handling provided by .NET, cleaning up the code, improving its maintainability, and, whenever possible, complying with .NET best practices. ...
|
-
|
Here is a quick way to know if a binary file (*.exe, *.dll, *.ocx, …) has a dependency on the Visual Basic 6.0 Runtime. If you are concerned about the VB6.0 runtime not being supported after Windows Server 2008 and Windows 7, this is a trick that can help you decide whether to keep a particular third party ActiveX component in your application through COM Interop after migrating to the .NET Framework or to start looking for a replacement in case the runtime is no longer available (and thus the component will no longer work)....
|
-
|
How Banamex, a leading Mexican bank, part of Citigroup, was able to migrate over 5 million lines of code from VB6 and ASP to C# and ASP.NET using the Visual Basic Upgrade Companion, in compliance with all corporate policies set for quality assurance and information security....
|
-
|
One of the key features of the Visual Basic Upgrade Companion (one that is not present in the Developer Edition, BTW) is that it’s functionality can be customized and extended. The VBUC includes three mechanisms to customize the generated code: Migration Profiles, Custom Maps and Additional Customizations....
|
-
|
Earlier this week we launched an joint initiative with Microsoft and Avanade in the UK for helping Visual Basic 6.0 developers move their applications to .NET. The initiative consists of several parts, including a web portal, hosted by Microsoft, and two offerings, a10% discount on the license for the VBUC + a free workshop with Avanade’s consultants, and the launch of the VBUC Developer Edition at a special price of £199....
|
-
|
Introducing the Visual Basic Upgrade Companion Developer Edition, a low-cost migration tool that allows you to migrate up to 50,000 lines of Visual Basic 6.0 code to either C# or VB.NET, at an introductory price of £199....
|
-
|
The Visual Basic Upgrade Companion is able to generate both C# and Visual Basic .NET code from the original Visual Basic 6.0 code base. Thus, when doing a migration project with our tools, you can choose either language. This decision is a challenge itself, especially if you aren't doing any .NET development before the migration....
|
-
|
If you are only migrating some components of your VB6 application to .NET, as part of a phased approach to the migration project, you will be happy to hear that the VBUC supports adding binary compatibility information to migrated ActiveX DLLs automatically....
|
-
|
We recently did some quick tests on the results of some projects that we just finished migrating to compare the binary size and memory footprint of the resulting migrated .NET application and the original Visual Basic 6.0 application. Here is a brief summary of the results....
|
-
|
Here is a brief summary of our experience regarding the performance of migrated .NET applications when compared to the performance of the original Visual Basic 6.0 applicaitons....
|
-
|
As I mention in a post last week, we recently released version 2.2 of the Visual Basic Upgrade Companion. The previous version, 2.1, added some new things, but mostly focused mostly on "under the covers" improvements, and fixing several issues reported with version 2.0. However, for this release, we do have several exciting new features that should make migrations from Visual Basic 6.0 go much smoother. Here is a brief summary, a "What's new" of sorts, for this new version....
|
-
|
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....
|
-
|
A few days ago we posted some new case studies to our site. These case studies highlight the positive impression that the capabilities of the Visual Basic Upgrade Companion leave on our customers when we do Visual Basic 6.0 to C# migrations....
|
|
|
|