This comment comes from: http://weblogs.asp.net/israelio/archive/2005/11/29/431788.aspx
" I had to migrate some vb6 app to Visual Studio 2005, I was very afraid things might stop working and that i will have lots of work to do after the conversion
B U T
Everything just worked great on first round!
It seems that someone in Redmond has done pretty good job on the conversion wizard as I now have vb.net app !
,,, hmm and don’t mistake me as a vb.net user its being translated as i write this post to c# :-)
"
Share your stories with us!
This is a recent interview with Jay Roxe, the Microsoft PM for Visual Basic .NET. You will find some good pointers on how to approach the migration.
Take a look: http://www.ddj.com/documents/s=9776/ddj1129914421813/swigart2.htm
Hi all!
I am continously looking for stories about Visual Basic Migrations. If you share a story with us I'll send you a very nice ArtinSoft beach handbag for your effort.
I want to know the good, the bad and the rest. The most interesting story will get an additional surprise gift.
Let's start sharing.
Oscar's BLOG is also another interesting resource for Visual Basic Migrations. Check it out and don't be afraid to ask questions. Oscar is super knowledgeable and willing to help.
http://blogs.artinsoft.net/ocalvo/articles/168.aspx
Enjoy, Federico.
<a href="http://www.technorati.com/claim/3y9amdvwm4" rel="me">Technorati Profile</a>
Upgrading Visual Basic 6.0 to Visual Basic .NET and Visual Basic 2005 guide is ready!!!.
The guide teaches you a predictable process that can be followed to migrate your Visual Basic 6 code to .NET. It contains a lot of experience from many migration projects and I am sure it will benefit your project.
This guide was developed jointly by the Microsoft patterns & practices team and ArtinSoft, a company with vast experience in Visual Basic upgrades and the developer of the Visual Basic Upgrade Wizard and the Visual Basic Upgrade Wizard Companion. This guide provides valuable information for organizations who are considering upgrading their Visual Basic 6.0-based applications and components to Visual Basic .NET. It provides proven practices to reach functional equivalence with a minimal amount of effort and cost and guidance for common advancements after the application is running on the .NET framework.
In addition to the guidance itself, a new tool, the Visual Basic 6.0 Upgrade Assessment Tool, is provided to give your organization assistance in identifying common upgrade issues and estimating the cost and effort required to upgrade your Visual Basic 6.0 code.
Let me know what you think!
The Visual Basic Upgrade Guide produced by the Patterns and Practices group at Microsoft and authored mainly by ArtinSoft consultants can now be downloaded in its integraf form from GOTDOTNET (http://www.gotdotnet.com/codegallery/directory.aspx enter the VB6 to VB.NET migration guide gallery).
You can also download the Visual Basic Assessment tool that will help you understand the effort required in a migration and it will also help you with the planning of a migration project.
I'd like to hear your comments. Is this new tool/guidance useful? Are you looking at migration projects with a different perspective?
Early feedback is very encouraging!
Episode 2 of the VB6 to VB.NET Cast is now ready and published at DDJ. Here are the links:
.NET Cast Site
http://www.ddj.com/podcast/dotnetcast/
Episode 2 MP3
http://www.ddj.com/documents/s=9887/ddj050921dnc/
Enjoy!
The following is an extract of an announcement that went public yesterday. It shows again the momentum around migrations. I am currently at PDC in Los Angeles and talking to ISVs, that are current VBA licensees, about how to approach the transition to the new technology. They all seem to like the automated migration approach in which they provide their customers with tools to help automate the process. What do you think? Let me know, let's explore the issue...
“ VSTA consists of an IDE used by ISVs to build VSTA support into an object model they can expose in their application, a runtime engine, and an end-user IDE which communicates with the object model. It includes a software development kit (SDK) for integrating a customer interface object model into the ISV application and an end-user IDE incorporating VB .NET and C#. The application then uses the .NET Framework Common Language Runtime (CLR) for development and production.
Recently, the level of investment made by VBA partners in their .NET applications has increased considerably. Many will decide to integrate VSTA into their existing VBA-enabled products and that, in turn, will create a strong demand among their customers for the migration of their VBA code to the .NET Framework.
ArtinSoft now provides its migration technology and expertise to ISVs who have integrated Microsoft VBA into their products and choose to integrate VSTA into their .NET applications. We have designed this new solution to meet the migration needs of VBA partners worldwide. The core of the solution is a recasting of the ArtinSoft VB Upgrade Companion in order to process VBA projects effectively and then efficiently convert them into fully natural VSTA solutions through the migration and restructuring of their original code. Summit Software 
, which has supported hundreds of VBA partners since 1996, has provided invaluable input into the design of our new solution. We are currently working closely with Summit to deliver this support program to the VBA community. “