We are sure that you will like to see what the VBUC can do for you.
-
You can take a look at our Reference Sample Application called Salmon King Seafood (SKS). This is a fictions company that sells seafood. We provide the VB6 code as well as the migrated code to C#, to .NET Core and to ASP.NET Core.
-
We also prepared with Microsoft an extended sample for their Tailwind Azure Demos this demo is a Point of Sale Application that is migrated from VB6 to Desktop and then to Azure.
Unlike a rewrite, VBUC moves existing back-end logic to the new platform, keeping proven and debugged logic and processes intact and dramatically reducing the total defects to be resolved following the migration.
There are several drivers for a VB to .NET migration:
Integrate Windows, Web, Office and Mobile solutions Boost system performance Ease deployment Improve the maintenance of an application Increase developer productivity Consolidate your company's valuable software assets Avoid obsolescence of outdated software support for VB 6 ended on April 8th, 2008 . Maintain competitive advantage
Upgrading Applications Written in Earlier versions of Visual Basic for example VB4 or VB5
The VBUC can also help you to modernize your Classic ASP WebSite.
-
[Split Config Files] (http://blogs.artinsoft.net/Mrojas/archive/2011/01/06/Split-Config-files-in-several-files.aspx)
Whenever you're trying to convert a VB6 or Classic ASP application to .NET with the Visual Basic Upgrade Companion it is recommended that you do so in an environment where the source application can be built and executed. This will ensure all the required references are correctly registered in that environment. Sometimes, however, VBUC will still show some errors in the "Resolve References" ....
An overview of the migrated code after upgrading from VB6 to Windows Forms
This article provides a lot of details on how to handle project references. In particular it provides some guidance for a VB6 application that was using the EXCEL APIs
How to use Context Sensitive help files in Windows Forms
In VB6 public variables defined in standard (.bas) modules aren’t really “global variables”. These public variables are scoped at the apartment level
In VB6, you need VBControlExtender object for dynamically adding a control to the Controls collection using the Add method
A post with some information about how the VBUC handles fixed length strings and windows apis
Some examples on calling DLLs when moving from VB6 to .NET
Binary Compatibility: In VB6 when you have an ActiveX Library it was very important to use the BinaryCompatibility setting to make sure that your applications did not break after a change.
Exposing C# Classes thru Interop
One of those subtle details is that the tlbexp tool (this is the tool that generates the .tlb for a .NET assembly) generates a prefix for enum elements.
-
Information about migrating Crystal Reports
-
Using Crystal Reports in VS
Quick replacement for the OLE Container Control that you had in VB6
Implementing Property Pages in VB.NET or C#
Creating a Windows Service in VB6
A list of some things that you should consider:
- Internationalization of Applications
- Internationalization Part 2
- [Internationalization Part 3] http://blogs.artinsoft.net/Mrojas/archive/2006/12/27/Starting-with-the-internationalization-bla-bla-(Part-Two).aspx
When a library a library has some classes, properties, methods or events that aren't already supported an Upgrade Stub will be generated. An Upgrade Stub is a "mock" class.
public class MSXML2_XMLHTTP30
{
public string getresponseText()
{
UpgradeHelpers.Helpers.NotUpgradedHelper.NotifyNotUpgradedElement("MSXML2.XMLHTTP30.responseText");
return "";
}
public void open(string bstrMethod, string bstrUrl, object varAsync, object bstrUser, object bstrPassword)
{
UpgradeHelpers.Helpers.NotUpgradedHelper.NotifyNotUpgradedElement("MSXML2.XMLHTTP30.open");
}
public void send(object varBody)
{
UpgradeHelpers.Helpers.NotUpgradedHelper.NotifyNotUpgradedElement("MSXML2.XMLHTTP30.send");
}
}https://www.mobilize.net/blog/vbuc-upgrade-stubs
-
A video walkthrough of our SKS reference application migrated all the way from VB6 to the WEB. Excellent video by John Brown.
-
Another live session migrating Tailwind Point of Sale App to Azure
-
[10 things to know about the VBUC] (https://www.youtube.com/watch?v=XuGqQBqzePY)
-
Comparison of original VB6 app with migrated WebMAP version showing how they are visually and functionally equivalent.
-
Moving legacy Windows desktop applications to a modern Web architecture involves a lot of issues. We discuss and give you ideas about how to handle them.