|
All things migrations, software and technology
Browse by Tags
All Tags » Visual Basic to .NET ( RSS)
-
|
In it March issue, Visual Studio Magazine published an in-depth article about legacy migrations called “Unlocking Legacy Code”. This article talks about the challenges faced by companies migrating from Visual Basic 6.0 to .NET, the drivers behind these migrations and the pros and cons of using an automated migration solution....
|
-
|
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)....
|
-
|
The business-oriented newspaper, El Financiero, just published an article talking about the advantages of performing a migration instead of a manual rewrite. ...
|
-
|
Yesterday TechNewsWorld published an article called Planning a Migration Route From Visual Basic 6 to .Net, which discusses some aspects of a a 2008 report by the Aberdeen Group on IT infrastructure outsourcing. The article contains lots of valuable information for those of you considering moving your VB6.0 applications to .NET, by giving a very good idea on the best practices performed by the “Best-in-Class” organizations. I wanted to touch briefly on some of the points made by the article, and how it matches our experience helping Fortune Global 1000 companies upgrade their applications to the latest technology....
|
-
|
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....
|
-
|
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....
|
-
|
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....
|
More Posts Next page »
|
|
|