Or just GTFO of this crappy programming language and use a real one :PQuote:
Originally Posted by WoF
Printable View
Or just GTFO of this crappy programming language and use a real one :PQuote:
Originally Posted by WoF
My, my. Hard words. What are YOU doing here, then?
You know, I can't. For professional reasons I have to stick to it. And I have come to love it, too. ;)
Hmm, well I am just starting to learn C++ and VB6 is the language I know like second best (PHP is my specialty and thats not useful for making programs), VB6 is just getting dated and it has all this compatibilty stuff I don't like. but if you need to stick to it for professional reasons I guess it's the best to get as good in it as possible.Quote:
Originally Posted by WoF
Right you are. That's what I'm trying to. :)
Sure I also start mingling with C# and looking into VB.NET, but I think I will not be able in near future to migrate the big application I have made in VB6 into one of those. I only hope it will still be supported furthermore by Microsoft operating systems.
Ye that's the only problem, microsoft discontinuing the functioning of vb6 apps. I just love C++ because it's multi-platform and it's more advanced then vb6, just need to get the hang of all the complicated OOP stuff etc in C++
For me, vb was my first language and my first love because of its rad environment. Then the shocking reality of C was the following semister and even though I know several other languages, I still use these various forums to keep my slowly dying love alive in my mind and don't bother with the rest...
Boy, this is very moving. *sniff* ;)
Well, in the past I used to do at least one project each in Fortran Cobol, Pascel (respectively Delphi) and some other (Pl/I for instance, PLM, both completely died away). In VB6 I did my largest project yet. It grew over the years and over the years got more features and less bugs, and now I have to maintain this quality, still expanding it. I can't help loving it.
Well here is to you and your race to retirement or should I say I hope you are able to retire before you are forced to upgrade your multiple year vb project to .h e l l :)
Good Luck
Here's to you, too. :)
As long as I can get it to run in Windows 7 I shall be save for the next years, I expect.
Although it seems not too impossible to completely migrate to VB.NET within 8 or 12 Months (as I'm doing that all alone), I'd rather avoid this. Automatic migration would surely fail, so I'd have to rewrite it piece by piece.
The problem is, within this time I guess VB2008 is outdated again and Windows FlyFly is coming on strong, get the Beta to test it, old API functions no longer supported .Net Framework 7.0 guides you through everything and even programmers can not anymore do what they want. And then it's time to retire.
VS2010 is a totally different animal. Take a look at the BETA
Does that mean I can already stuff up my new VS2008 which I hardly ever touched to play with, yet?
Not really. The editor is now WPF, so you can zoom and scroll easier. Adds a few features, like Net 4.0
*gulp*
Until I get to know VS2008 better, VS2010 will be antiquated, I guess.
Not even due until Feb, 2010, I think. Just hit Beta 2
You think I should drop my new VS2008 for the 2010 beta version? I don't know.