|
-
Oct 17th, 2005, 12:09 PM
#1
Re: Moving to VB.NET from VB6
You dont have to distribute the framework if you dont want to. Your setup package can download it if its not automatically detected. You can target your app for a particular FW version so you can be compatible. There are only 2 version that are targets - 1.0 and 1.1. With 2005 there will be 2.0 but its not backwards compatible. Having to target between 3 versions is not hard like having to deal with dll hell with vb6.
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 
-
Oct 17th, 2005, 12:44 PM
#2
Thread Starter
Fanatic Member
Re: Moving to VB.NET from VB6
 Originally Posted by RobDog888
You dont have to distribute the framework if you dont want to. Your setup package can download it if its not automatically detected. You can target your app for a particular FW version so you can be compatible. There are only 2 version that are targets - 1.0 and 1.1. With 2005 there will be 2.0 but its not backwards compatible. Having to target between 3 versions is not hard like having to deal with dll hell with vb6.
Thanks. Unfortunately, the schools we do business with are equipped with computers which are not exactly state of the art. Some of them aren't even connected to the Internet.
Most of the software we develop deals with testing (particularly, multiple choice questions).
To tell the truth, I see no valid reason for us to switch to .NET but I need to convince my boss. While developing our applications in VB5/6 takes very little time, producing the same software in .NET would take at least twice as much, considering the learning phase. For what? We can do all we want in VB5/6 and, unless we need something that classic VB cannot create, it wouldn't make any sense to upgrade for the sake of upgrading.
-
Nov 5th, 2005, 02:06 AM
#3
Thread Starter
Fanatic Member
Re: Moving to VB.NET from VB6
Hello, I would like to "reverse" my original question: could you please help me make a list of good reasons why my school should NOT upgrade to VB.NET?
Please read my previous posts in this thread to see what the situation in my school is like.
I have already made clear that I am against the idea of switching to VB.NET but I need to convince my boss with documentary evidence supporting my point of view.
Any help will be appreciated.
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
|