VBRun - The VB 6.0 Resource Center
It has been a busy week and a half. In the last week I completed moving my family from the East Coast to the West Coast and at the same time worked with many others here at Microsoft to finish off the VBRun site.
This has been a project that has been in the works for some time now. The goal was to create a place within MSDN that we could bubble up the vast amounts of VB 6.0 content that we had and combine other VB 6.0 content. With the rise of VB.NET many sites, including MSDN, have migrated from VB 6.0 to VB.NET. Finding VB 6.0 content has been a random search of the web.
Our goals for this site where two fold. First to solve this problem and attempt to bring as much VB 6.0 content together in a single location to allow developers to easily find what they need to get their jobs done.
The second goal was to provide good content around using VB 6.0 and VB.NET together. There is so much misinformation and misconception that it is either VB 6.0 OR VB.NET. I don't believe that is true. Both VB 6.0 and VB.NET can live side by side on a computer. This is not the limit however, VB 6.0 and VB.NET can live side by side in the same application. The VB fusion section was designed to help developers make the migration from VB 6.0 to VB.NET as easily as possible while maintaining their existing VB 6.0 code base and blending it with VB.NET going forward.
The third section of the site is related closely to this and that is migrating the developer's skills. This is all about training and learning. VB.NET is not VB 6.0 but it is not a radical departure either, the truth is somewhere down the middle. Is it as simple as VB 5 to VB 6 no, but it not as different as VB 6 to C# or VB 6 to Java. (Please spare me the comments from both sides screaming it is a massive change and the reply that it is a simple change.) Our goal here was to provide you with as much information as possible to allow you to be the most productive developer and help you maintain a marketable skill set.
This site is a work in progress. We have additional plans and ideas but would love to hear your feedback on what you see so far and where you would like to see things go in the future.