Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 390
  • Last Modified:

Resource for Converting from Visual Basic 6.0 to Visual Studio 2005

Hi,

I just converted two small projects from Visual Basic 6.0 to Visual Studio 2005.  After resolving the 300 upgrade warnings, my project is running just like before.  However, I am interested in updating the conventions I use in programming.  Is there a good resource that compares Visual Basic 6.0 to Visual Studio 2005 and provides the "newer" methods.  For example, is there a better way to connect to data sources than ADO with Visual Studio?  

Thanks
0
tlchavet
Asked:
tlchavet
2 Solutions
 
MattiCommented:
Hi!

ADO .NET, there is a sample:
http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=5854&lngWId=10

If you use old ADO it needs interop dll for it, this latest user framework.

Matti
0
 
jpaulinoCommented:
You can go to MSDN webpage and you will find videos, webcast, etc
http://msdn2.microsoft.com/en-us/vs2005/aa700853.aspx

or download this free books
Introducing Microsoft Visual Basic 2005 for Developers
http://msdn2.microsoft.com/pt-br/vbrun/ms788235.aspx

Upgrading Microsoft Visual Basic 6.0 to Microsoft Visual Basic .NET
http://msdn2.microsoft.com/pt-br/vbrun/ms788236.aspx
0
 
tlchavetAuthor Commented:
Is there a good reference book out there on Visual Studio?
0
 
tlchavetAuthor Commented:
Thanks a bunch for the information!
0
 
Mike TomlinsonMiddle School Assistant TeacherCommented:
"I am interested in updating the conventions I use in programming."

Hi tlchavet,

I would take it to a whole other level.  Try not to focus on simply what is the "equivalent" syntax, or what library do we use instead of the old one from VB6.  Instead, to really leverage the power of the VB.Net you need to change your entire methodology!  You must learn to think in terms of TRUE object oriented programming.  Though it is sometimes possible to convert old code and make it work as it did before...many times if that same app was developed from the ground up in .Net it would have been designed completely differently because different technologies were available.  VB6 was only a "pseudo" object oriented language, and as such, forced us into doing things in ways that don't always work well in .Net.

Try to find some VB.Net books that focus on designing with OOP in mind.  Unfortunately I don't have any to reccomend as most of my experience is from the "self taught" camp.  =\

~IM
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now