Matthew MacDonald

Subscribe to Matthew MacDonald: eMailAlertsEmail Alerts
Get Matthew MacDonald: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by Matthew MacDonald

The .NET Framework is stuffed full of treats for the VB developer. Long-awaited improvements such as strict type checking, structured exception handling, and true object-oriented support extend the power of the language dramatically - but at a price. The only way a Visual Basic 6 program can be brought to the .NET world is through a painful migration process that rarely runs without incident. In this article, we'll consider some of these ugly problems - and the insights you can gain from them. Interop Versus Migration You may have already read about RCW (Runtime Callable Wrappers), which allow .NET programs to easily, elegantly communicate with legacy COM components. .NET really shines in all aspects of COM interoperability. However, there's been much less written about a far thornier problem: migrating legacy VB code into a VB.NET project. For VB programmers, this ... (more)