I find it always interesting that new ways to postpone the VB6 migrations are introduced. the title of this post is the combination of an Infoworld and an Eweek article on the subject. I understand where a tool (Microsoft InteropForms Toolkit 1.0 ) that attpepts to tempt VB6 developers use .NET while retaining a safety net in VB6 is coming from. The whole idea is to reduce the risk, to make a transition smoother. But are we really achieving the business benefits by doing it? I think it goes all back to the fact that people do not believe an automatic migration from VB6 is possible. I firmly believe it. If you have followed this blog, you probably believe it too. In any case, every effort in the direction of helping customers move is laudable!
Look at the Infoworld article: http://weblog.infoworld.com/techwatch/archives/008022.html
or the Eweek article: http://www.eweek.com/article2/0,1895,2019386,00.as...