Great News! VB6 support likely to continue into Windows 12
-
VB6? Was that the one that came with a chisel and a tablet of stone for an IDE?
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
I'm not positive that the chisel had been developed yet. VB6 wasn't up to that job.
"Never attribute to malice that which can be explained by stupidity." - Hanlon's Razor
-
Couldn't see this mentioned anywhere.
VB6 just got an important boost from Microsoft blogger Scott Hanselman. In his post (bit.ly/2rcPD0f), Hanselman shows how to configure a VB6 app to be hosted in the Windows 10 Store, using the Microsoft Desktop Bridge infrastructure and tools (bit.ly/2HFVzcc). That’s huge, as hosting an app in the store means that Microsoft is at least somewhat vouching for its compatibility and content. Potential purchasers perceive it as sort of a Good Computing Seal™
Real programmers rejoice!
People bash things they do not understand. I wrote an application in VB6 that interfaces with Avaya phone systems and also had instant messaging and file sharing. It worked great and might even still be in use. Just because you don't have the most expensive tool does not mean you can't build something beautiful.
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
Couldn't see this mentioned anywhere.
VB6 just got an important boost from Microsoft blogger Scott Hanselman. In his post (bit.ly/2rcPD0f), Hanselman shows how to configure a VB6 app to be hosted in the Windows 10 Store, using the Microsoft Desktop Bridge infrastructure and tools (bit.ly/2HFVzcc). That’s huge, as hosting an app in the store means that Microsoft is at least somewhat vouching for its compatibility and content. Potential purchasers perceive it as sort of a Good Computing Seal™
Real programmers rejoice!
I can see how large legacy VB6 code-bases would continue to be retained as-is, because re-writing it into a managed framework is a huge ask. What I don't get it why new code would ever get written in VB6, with the lack of support, limited availability of engineers who've used it, etc.
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
-
People bash things they do not understand. I wrote an application in VB6 that interfaces with Avaya phone systems and also had instant messaging and file sharing. It worked great and might even still be in use. Just because you don't have the most expensive tool does not mean you can't build something beautiful.
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
Most people bash VB6 programmers rather than the language because back when it was popular, it was so easy to get started with that it attracted a lot of relatively unskilled programmers. Also, those days, C and C++ were considered the de-facto real programming language on Windows. And anyone not doing in-code memory management was considered a dummy. Ironic that both VB6 and C++ got eliminated by memory-managed language frameworks like C#, JS, and VB.NET :-)
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
-
I can see how large legacy VB6 code-bases would continue to be retained as-is, because re-writing it into a managed framework is a huge ask. What I don't get it why new code would ever get written in VB6, with the lack of support, limited availability of engineers who've used it, etc.
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
-
People bash things they do not understand. I wrote an application in VB6 that interfaces with Avaya phone systems and also had instant messaging and file sharing. It worked great and might even still be in use. Just because you don't have the most expensive tool does not mean you can't build something beautiful.
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
Quote:
Just because you don't have the most expensive tool does not mean you can't build something beautiful.
VB6 was expensive. VB.NET is mostly free. Beauty is in the eye of the beholder :)
-
Quote:
Just because you don't have the most expensive tool does not mean you can't build something beautiful.
VB6 was expensive. VB.NET is mostly free. Beauty is in the eye of the beholder :)
-
Couldn't see this mentioned anywhere.
VB6 just got an important boost from Microsoft blogger Scott Hanselman. In his post (bit.ly/2rcPD0f), Hanselman shows how to configure a VB6 app to be hosted in the Windows 10 Store, using the Microsoft Desktop Bridge infrastructure and tools (bit.ly/2HFVzcc). That’s huge, as hosting an app in the store means that Microsoft is at least somewhat vouching for its compatibility and content. Potential purchasers perceive it as sort of a Good Computing Seal™
Real programmers rejoice!
-
I can see how large legacy VB6 code-bases would continue to be retained as-is, because re-writing it into a managed framework is a huge ask. What I don't get it why new code would ever get written in VB6, with the lack of support, limited availability of engineers who've used it, etc.
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
The new VB6 code happens when those large legacy apps need minor updates or changes. At any given point, it's a lot less work to add a bit of code to the existing application than to do a re-write. And so new VB6 code continues to be written, year after year. I wouldn't be surprised if there's some poor soul in 2035 who is still plugging away making updates and additions to a legacy VB6 app. Although at that point, such a person might be able to charge some hefty consulting rates for working in VB6. So perhaps this person would more more of a tortured soul than a poor soul...
-
The new VB6 code happens when those large legacy apps need minor updates or changes. At any given point, it's a lot less work to add a bit of code to the existing application than to do a re-write. And so new VB6 code continues to be written, year after year. I wouldn't be surprised if there's some poor soul in 2035 who is still plugging away making updates and additions to a legacy VB6 app. Although at that point, such a person might be able to charge some hefty consulting rates for working in VB6. So perhaps this person would more more of a tortured soul than a poor soul...
A tortured soul billing $300/hour sounds pretty doable to me. :rolleyes:
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
-
CHill60 wrote:
VB6 was expensive.
How so? It was free when I was using it, as I recall.
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
VB6 was never free as far as I can remember. You could either buy it as part of Visual Studio (including VC++) or you could buy it standalone (not sure if that was earlier versions though).
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
-
CHill60 wrote:
VB6 was expensive.
How so? It was free when I was using it, as I recall.
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
I'm not positive that the chisel had been developed yet. VB6 wasn't up to that job.
"Never attribute to malice that which can be explained by stupidity." - Hanlon's Razor
-
I can see how large legacy VB6 code-bases would continue to be retained as-is, because re-writing it into a managed framework is a huge ask. What I don't get it why new code would ever get written in VB6, with the lack of support, limited availability of engineers who've used it, etc.
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
If VB6 is truly unsupported at this point, then you just need one serious-enough exploit in the runtime to end its use. OTOH: - See Windows XP - You'd hope those systems still in production and relying on it aren't connected to the internet in any way, shape or form - mitigating that problem - Aren't store apps supposed to be running in a completely sandboxed environment? OTOH (yeah, that'd be a third hand I guess): - Despite all this, I have no doubt there's plenty of VB6 exploits being abused right now, and will continue for the foreseeable future
-
If VB6 is truly unsupported at this point, then you just need one serious-enough exploit in the runtime to end its use. OTOH: - See Windows XP - You'd hope those systems still in production and relying on it aren't connected to the internet in any way, shape or form - mitigating that problem - Aren't store apps supposed to be running in a completely sandboxed environment? OTOH (yeah, that'd be a third hand I guess): - Despite all this, I have no doubt there's plenty of VB6 exploits being abused right now, and will continue for the foreseeable future
The extent of damage would be minimal since VB6 is mostly used for desktop UI apps.
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
-
alang_icon wrote:
I think support in this case means Microsoft tests the old code against new Windows versions.
No, it doesn't, and no you don't. VB6 is a dead language, and has never been excellent.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Eddy Vluggen wrote:
VB6 is a dead language, and has never been excellent
You take that back!!
cheers Chris Maunder
-
The extent of damage would be minimal since VB6 is mostly used for desktop UI apps.
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
-
Doesn't matter what the app is used for, if you can crash an app and control the return address, you have a way to run any native code of your choosing.
Yeah, on an end user's desktop. Minimal damage.
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
-
Eddy Vluggen wrote:
VB6 is a dead language, and has never been excellent
You take that back!!
cheers Chris Maunder
Aight, then, it is "resting". Monty Python - Dead Parrot - YouTube[^]
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.