|
-
May 3rd, 2006, 10:00 PM
#8
Re: Leaving VB6
Well it sounds like you do independant work so it may not matter which you use as the client usually doesnt see the code.
Going from VB6 to VB.NET itself is difficult to un-learn some bad programming habbits. So C# may be easier to learn for you but in my opinion its slower as you have to type in the correct case and a few minor things take a little longer to get used to as compared to vb.net. I am glad I went from VB6 to VB.NET as that worked best for me.
Spend a little time on each language of the same project to be able to see the differences for yourself.
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|