Show Posts
1
Ultra Hal 7.0 / Ultra Hal's future
« on: August 15, 2009, 02:20:31 pm »
I know I'm not very active here, I spend most of my time on the forums reading. I'm a big fan of Ultra Hal, and I have used Hal since version 4.
This has had me thinking for quite some time now; I recall hearing that Ultra Hal was made using Visual Basic 6; is there any plan in the future to upgrade to the new framework or to another language?
The reason I'm asking this, is because support for VB6 is dwindling.
Windows 7 will still be able to handle VB6 (though you need to install the VB6runtimes, which don't come default with Windows7 or Vista), but after that, Microsoft's operating systems won't support vb6-applications anymore.
To quote Paul Yuknewicz, the VB6 Program Manager that worked on VB6 at Microsoft:
"VB6 runtime will be shipping and supported as a part of Windows 7, however there are no plans to ship it in future versions of Windows."
He had 4 reasons:
Migration is perceived as expensive, Migration is perceived as lacking value, VB6 Applications are not evolving, Applications will be retired before VB6 stops working, It’s just procrastination, and There’s just too much VB6.
Here is the source for that article:
http://blogs.artinsoft.net/fzoufaly/archive/2009/01/13/vb6-runtime-will-be-supported-on-windows-7-but-no-plans-to-support-it-on-future-version-of-windows.aspx
This has had me thinking for quite some time now; I recall hearing that Ultra Hal was made using Visual Basic 6; is there any plan in the future to upgrade to the new framework or to another language?
The reason I'm asking this, is because support for VB6 is dwindling.
Windows 7 will still be able to handle VB6 (though you need to install the VB6runtimes, which don't come default with Windows7 or Vista), but after that, Microsoft's operating systems won't support vb6-applications anymore.
To quote Paul Yuknewicz, the VB6 Program Manager that worked on VB6 at Microsoft:
"VB6 runtime will be shipping and supported as a part of Windows 7, however there are no plans to ship it in future versions of Windows."
He had 4 reasons:
Migration is perceived as expensive, Migration is perceived as lacking value, VB6 Applications are not evolving, Applications will be retired before VB6 stops working, It’s just procrastination, and There’s just too much VB6.
Here is the source for that article:
http://blogs.artinsoft.net/fzoufaly/archive/2009/01/13/vb6-runtime-will-be-supported-on-windows-7-but-no-plans-to-support-it-on-future-version-of-windows.aspx