Guest Muratti Posted October 2, 2002 Posted October 2, 2002 Hey, I have a not sophisticated VBA code (integrated with Excel) that I would like to convert into VB.Net. I have some questions: Is the VB.Net Upgrade wizard applicable to convert VBA code as well? How hard is it to convert to VB.Net? SHould I first convert to VB6 and then to VB.Net? I would really appreciate if anybody would help me. Thanks. Quote
Guest KidCoder Posted October 7, 2002 Posted October 7, 2002 I think the convert wizard should be compatible with VBA. All you have to do to find out is open your VBA project in VB.NET. It's not hard to migrate - it does it automatically. :) You convert it to VB6 first ONLY if the wizard isn't compatible with VBA. Welcome to We're Here! Kid Quote
*Gurus* divil Posted October 7, 2002 *Gurus* Posted October 7, 2002 It's important to note that it is always better to rewrite, rather than convert. You learn more that way, and if you don't have time to rewrite, the project is probably left in whatever it was before. Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
Guest KidCoder Posted October 7, 2002 Posted October 7, 2002 It's true that it's better to rewrite instead of convert, but I've learned a lot more about coding structure of .NET much faster by migrating all my projects, and then studying the coding differences. It's almost like my own .NET forum! :D Quote
*Gurus* divil Posted October 7, 2002 *Gurus* Posted October 7, 2002 Except that the conversion wizard doesn't convert to real .NET, it uses helper functions in the VB compatibility namespace which I don't think is redistributed. Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
Guest KidCoder Posted October 8, 2002 Posted October 8, 2002 OH! I didn't know that! I'll have to show this thread to my uncle, because he seems to think that it's real .NET. Thanks! Quote
*Gurus* divil Posted October 8, 2002 *Gurus* Posted October 8, 2002 It's real .NET, but often a rather perverted version, designed to look more like VB6 code. This avoids the conversion wizard having to jump through hoops when processing old code. It's always better to get a book, and read up on how a new topic is done in VB.NET then rewrite. More fun too! Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
Guest KidCoder Posted October 8, 2002 Posted October 8, 2002 Alrighty, thanks. I think I can mooch a book off of my parents. :p Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.