I found that MSV6 (VB and C++) still work well on XPSP2.
So I'm not sure in the future since .NET was released since few year ago.
What info which I should consider to move from MSV6 to .NET
Now, I'm developing on XPSP2 and 2K Server and 2K DC.
Newbi for .NET
Hot Topic
- Running an application
- How do I map a network drive in VB 2005?????
- Handle TargetInvocationException (Vb.NET Beta2)
- Debugging problem.
- System.Runtime.InteropServices.COMException (0x800A03EC): Cannot access xls file
- Enabling f8 (debugging) in vs2005 beta1
- vb.net and crystal report
- A complex coding for me
- Give Me A Liitle Help Here Please.
- How to manage / call methods, procedures, forms in multiple Modules, classes, ect.?
Visual Basic
- HowTo enable SQLConnection&DataAdapter objects on a design window Webservice class
- disable pop-up
- Validating within a User Class
- openfiledialog default view
- Radio Check Options in Menu Strip?
- Can't directly dim an instance of a tableadapter 2005
- drawing lines on form
- VB Database program wants to go world wide web
- Installing Windows Service programatically
- help with vb.net
Newbi for .NET
QuetzalNeTGt
VB6 support has ended
VB.NET is a much better language than VB6.
It is, however, different enough that I believe it's a tough learning curve initially, and certainly a lot of legacy stuff is supported, but should not be used if you can help it.
The wizard to move VB6 apps to VB.NET is apparently not very good
VB.NET continues to evolve and grow, and will continue to have new features, both language and IDE. VB6 is dead in this sense
VB.NET offers all the benefits of the .NET runtime, and can interop with C# and C++ quite easily. However, it does mean your apps require the .NET runtime.
If I were a VB6 developer, I would have moved to VB.NET a long time ago, and I'd certainly be doing it now if I hadn't already. You can still use VB6, but there's no reason to lock yourself into a dead language exclusively.
TP Robinson