|
All things migrations, software and technology
Browse by Tags
All Tags » Visual Basic 6.0 ( RSS)
-
|
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)....
|
-
|
As you are probably well aware, along with the release of Windows 7 RC came some big news that affect Visual Basic 6.0 applications: Professional and Ultimate Editions of Windows 7 will feature a Windows XP Mode for backwards compatibility with legacy applications. Even in the scenario that XP Mode is supported for a long time, you still have to consider it as something that can be used for a smooth transition while you upgrade your applications to the .NET Framework, and not as an excuse for not upgrading....
|
-
|
This week Microsoft updated its support statement for Visual Basic 6.0 to include the upcoming Windows 7. Even though the original idea was to not support VB6 in Windows 7, given the outstanding demand, the runtime WILL BE included in the OS. Here's a brief summary of the latest changes....
|
-
|
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....
|
-
|
Today we published a new White Paper, Planning a Successful VB to .NET Migration: 8 Proven Tips. In it, we share some tips on things that you should be aware of when migrating your applications. Following them will help you ensure the project's success....
|
-
|
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....
|
|
|
|