![]() |
![]() |
![]() |
Longhorn Visual Basic compatibility I assume that Microsoft will release a version of Visual Basic once Longhorn releases.
Karthik
When i say executables, i mean "Can Visual Basic Longhorn run on old OS's?'.
Karthik
"I assume that Microsoft will release a version of Visual Basic once Longhorn releases. "
Almost Anonymous
VB6 is dead, there will be no updates. VB.NET will definitely be updated but software developed with it wont run on Win95 and probably 98/ME soon. Your best option is to use Delphi which is still releasing Win32 versions as well as .NET versions of the compiler. That would provide the easiest upgrade path.
Craig
hi
bui van hai
The real question is, will Visual Basic.NET Longhorn Edition (or whatever they choose to call it) make it easy to write "fat GUIs" that can run natively in Avalon *and* the old S.W.F. or GDI?
Iago
>> "VB6 is dead, there will be no updates."
Please stay informed more than you currently do. Thank you for your support.
== "VB6 is dead, there will be no updates." ==
I'd like to buy a clue, Pat.
Well there will not be a VB 7.0.. which I believe it was the person meant by "no significant updates".
Almost Anonymous
"VB6 is dead" <> "there will be no updates"
Kyralessa
I thought there was going to be an update to VB6 in VB 2005 -- that they were going to support the 'older' VB6-ish object model. Not so?
AllanL5
Either way, I just wish someone would take that tired old dog of a language- VB6 - to the knackers yard and put it out of it's misery!
TheGeezer
Man, it is not just that the language of VB6 sucks, the IDE is good for shit and the VB6 has tons of bugs, there are ways to work around those bugs but they are still annoying.
James Thomas
You know - VB6 is soon to go away. Sure! So (eventually) will cars and even toilets. And yes - even .Net. One day the internet (if it hasn't itself been replaced with something more wiz-bang) wil lbe cluttered with ".Net is shit" and "C# is loaded with bugs".
VoodooTree
|