|
Only start to worry if you sign a partition to bring back Clippy.
// TODO: Insert something here Top ten reasons why I'm lazy
1.
|
|
|
|
|
|
yacCarsten wrote: sign a partition
Been working with disks much lately?
|
|
|
|
|
// TODO: Insert something here Top ten reasons why I'm lazy
1.
|
|
|
|
|
I have an image of Clippy popping up on your screen with
"It appears that you meant to say 'petition'. Can I help you with that?"
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
// TODO: Insert something here Top ten reasons why I'm lazy
1.
|
|
|
|
|
You realize this means you'll also be able to go back to your 6 meter social distancing.
|
|
|
|
|
Yes, the 2 meter was a bit too close to my taste.
Actually, I did not get the vaccine (it was only for the Microsoft plot joke) and will probably not get it before July - France is *a bit* late on track.
|
|
|
|
|
GWBasic predated windows. VB4 was mostly just GWBasic with a code generator. The code generator for Windows had gotten fairly good by that time. When they got to VB6 they had added a lot of object oriented features. Where did VB5 stand in this evolution. Was it closer to 4 or 6?
So many years of programming I have forgotten more languages than I know.
|
|
|
|
|
I’d say it was closer to 6. 3 and 5 stand out for me as the best versions of VB (others can add the joke they desire here). 4 was an OLE-ification, and 6 was the attempt at web. (And 5 was the addition of classes)
TTFN - Kent
|
|
|
|
|
I did a lot of GWBasic then jumped into C++ 4 and a lot of embedded work. Never did much VB until 6 and then it was mostly VBA for Excel and other programs. VBA is mostly VB6. After that it has been .NET and C#. I have skipped over a lot of small steps in my career.
I am asking this question because I am just finishing up converting a VB4 program to a WPF and C#. Now they are giving me a VB5 conversion. I am kind of wishing I had screwed up the VB4 conversion.
So many years of programming I have forgotten more languages than I know.
|
|
|
|
|
Whole parts of my brain just opened up, creaking and dusty, at the mention of GWBasic.
Good memories...
cheers
Chris Maunder
|
|
|
|
|
Do not forget the cobwebs. I glad yours were good. When I started in on the VB4 upgrade I found the memories painful.
So many years of programming I have forgotten more languages than I know.
|
|
|
|
|
Exactly. Let sleeping dogs lie. Don't revive those poor abused brain cells.
|
|
|
|
|
Good memories?
Cheers,
विक्रम
"We have already been through this, I am not going to repeat myself." - fat_boy, in a global warming thread
|
|
|
|
|
5 was closer to 6
Real programmers use butterflies
|
|
|
|
|
So maybe the reason 7 8 9 is that they were not as close as 5 and 6.
|
|
|
|
|
In another universe they never developed .NET They have versions of 7, 8, 9 ... That universe is often know as DLL Hell.
So many years of programming I have forgotten more languages than I know.
|
|
|
|
|
Closer than what?
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
VB5 is closer to VB6 than it is to VB4. VB4 didn't do native compilation, IIRC and it still had a 16 bit support portion, again if i remember correctly.
Real programmers use butterflies
|
|
|
|
|
I was being a smart-ass. I actually don't care about VB...
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Who does? TBH it's just useless trivia I know from the bad old days.
Real programmers use butterflies
|
|
|
|
|
Deffo closer to 6 ... I still have a copy of Connell's "Visual Basic 5 from the Ground Up" and the VB6 Manuals. Just to remind me of my roots
|
|
|
|
|
If I'm not mistaken (it's a long time ago), there was one BIG change in 5 that stood out from all the rest: The GUI. Before 5, the GUI had consisted of a lot of loose windows spread over the desktop, and you could see the desktop and other open programs in the background (same was true for Delphi in the first versions).
From 5 and onward, the GUI changed, and you had ONE main MDI parent form open in which you had the other forms and panels, just like now in VS.NET.
I loved that, because that made it much cleaner and more easy to navigate around in.
Anything that is unrelated to elephants is irrelephant Anonymous
- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944
- Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain
|
|
|
|
|
michaelbarb wrote: Where did VB5 stand in this evolution. Was it closer to 4 or 6? IMO, VB5 was closer to VB6.
VB4 added classes, and added 32-bit support in addition to VB3's 16-bit.
VB5 was 32-bit only, added the ability to create controls, and compiled to native binary. It was part of Visual Studio 97, Microsoft's first attempt (AFAIK) at an integrated development environment.
VB6 added the ability to create web applications. It was part of Visual Studio 6 -- Microsoft standardized on v6 for all included products, as I recall VB6 had the highest version.
I don't recall that the core language changed much between versions. Unlike recent versions of C#, the big difference between versions was major additions to capabilities.
VB4 applications would compile in VB5, and IIRC, in VB6. Compiling down worked unless the program used features not available in the earlier version of VB.
How does one "convert" a VB program to C#? Circa 2003 I tried migrating VB6 programs to VB.NET, and that was a dismal failure -- it was much faster to completely rewrite the program in VB.NET than to try fixing the migrated version.
I'm picky on wording as it affects my response. If you're re-writing the programs, as long as you can read the intent of the VB code, I don't believe it will make much differences in what version the original program was written in.
Note: just for the heckuvit I searched on VB to C# converters -- I found several products that claim to do it. My first thought was "why?", as VB6 has been unsupported for 12 years and effectively dead for 15+ years. However, in the "top 20 languages" surveys I've read over the last few years, VB typically ranks 12 to 15. There's a LOT of VB programs out there, and management isn't going to pay to convert a program unless it's broken ....
|
|
|
|