-
For years, I've been writing code mostly in VB and some in C++. Some of these apps were months or even years in the making. Now, all of a sudden, Microsoft has not only decided to vastly change VB itself (VB.NET), but also to release a new 64-bit Operating System (Windows XP) to boot! OK.......Here are my questions:
1) Will my "old" 32-bit apps run ok on Win XP?
2) If not, will enough people continue to use current windows versions so as to keep me and others from starving?
3) Should I continue to write in VB6pro/SP5 or just say screw it and wait for VB.NET? I'm actually very comfortable with my current VB, it works great for most of the kind of stuff I write and use, and I have VC++ to satisfy the need-for-speed. If I have to re-write everything I've done over the past few years just to satisfy some new whim of Microsoft for an op system that "Bubba" can more easily interact with, I'm gonna be really Pi**ed!
Anyway, what does everyone think? Shall we keep on keepin' on with VB6 and VC++ v6 or are we just wasting our time?
- Radar
-
it would make sense that all your apps will work on the XP, if they dont, you will here lot of complaints
about your question in developing more vb
vb6 > vbNET is different
infact there i conversion tool (BUT it wont work properly if you had anything in vb 6 that was dropped in vbnet)
my suggestion is you write your apps in vb6 for now
BUT look at what has changed, meaning dont use anything in your app that will be dropped in the next version of vb..
read more on vbnet
-
1)Will my "old" 32-bit apps run ok on Win XP?
Does your software currently run on Windows 2000? Because that is what XP kinda is, Windows 2000 with a more user friendly interface. So basically your programs will have to be compatible with an NT based system. Which most VB programs would be, unless you used certain API's that are not used/compatible with an NT system.
Honestly I like XP, a lot. They took many of the good things from 2000, stability, networking power, faster speed, cooler windows, and more that I can't remember (But they also took the ungodly system requirements also). Plus whatever did not suck from ME, better user interface, more multimedia power, better direct x ability, etc. I can not wait to see the final version of it.
2)If not, will enough people continue to use current windows versions so as to keep me and others from starving?
Did everyone move up to ME when it came out? No. So there are still going to be a lot of people that can use the old programs. It's like I said though, most of your programs should work fine in XP.
3) 6 vs .net?
I can't answer that question because I have not seen the .net version yet.
-
Just as a Heads up!
Windows XP has taken down our entire network on 3 ocasions! I am in a LARGE company!
In all 3 cases they found the machines with the XP Beta in them causes major network porblems.
We have now been told if your machine has XP on it you will be Removed from the company network and charged!ZOINKS!
hmmmm....You can come to your own conclusion.
-
Yes...conclusion...don't use beta software in a production environment, which is EXACTLY what MS say in the licence agreement!
-
Thanks guys............You've all eased my nervousness somewhat (problem is now medical due to the large amounts of caffine that I consume :)). Technocrat - yep, been testing all my apps on Win 2k and have been careful about testing API calls,etc. I like Win 2k - its pretty cool. The reason I asked about XP is cause I got the impression from the MS site that since XP is 64-bit, it will be like 32 vs. 16-bit again. Oh well. Guess I'll have to try it and see. I just didn't want to write a bunch of new stuff for a dead market - its already bad enough as-is.
-
Don't worry about 64bit. There are too many 32bit computers out there in the world to just have it up and die. The opposite is probably true: 64-bit will probably be the one starving. WinXP is being creating for both 32bit and 64bit, so use the 32bit version and no worries. Plus, the 64bit version will be able to run 32bit apps (for the most part).
Try not running beta software in a critical situation. Look up the definition of beta.
-Incredulous
-
We have to evolve at some stage. I'm guess (I don't know because I wasn't in this business back then) but they're was probably all this hoo-har when Win32 hit the streets. Everyone with VB3 was probably like "OH NO!!!" Evolution happens, one of those things. I'll be sorry to see my cosy VB6 become obselete though...:(
