#Microsoft silverlight end of life code#
#Microsoft silverlight end of life Pc#
#Microsoft silverlight end of life windows 8#

Or at least in any way I ever heard about it. They just stopped updating things and never told anyone. Even the Zune music player app (standalone - wouldn't buy one of those MP3 trainwrecks) was a superior experience to some of the other music players available at the time: cover art animations, etc. It wasn't a bad product at all, but they ghosted us there as well.

#Microsoft silverlight end of life Pc#

Windows Media Center was one of them as well - it was essentially a free DVR we had, if we had a PC (and bought a cablecard tuner). They did the same for a bunch of other technologies. A popular search on Google for a while was 'Is Windows Workflow Dead?' Seems we weren't alone.

NET Framework versions, but nothing written down. It still was released with new releases of their IDE, and updated for their. When we'd ask Microsoft vendors, they would 'look into it', but they would never end up saying anything. There was no official stop of support, no blog postings, documentation, etc. There was a Microsoft technology called Windows Workflow Foundation that our company heavily invested in. Microsoft did have to abandon Windows Mobile later on, but it's not that they did not try as much as they could, and nobody in the right mind would think it was certain to succeed. There was a hilarious excuse used (he said the Maemo/Meego strategy could only lead to 1-2 major phone releases per year - yeah, who wants to be like Apple!) and almost all developers abandoned ship. Stephen infamously sent the 'burning platform memo', the costliest memo in corporate history, abandoning the strategy and switching to Windows Mobile. Nokia was transitioning from Symbian to Maemo/Meego at the time and had promised a smooth transition to developers with both platforms supporting Qt. They sent their own Stephen Elop to take over Nokia, destroy it so that Microsoft can buy it cheap to do their mobile phone experiment. Microsoft HAS been involved in the worst developer abandonment ever though, but in an indirect way. Besides, whoever invested heavily in Silverlight was not very bright in the first place. Oh, come on, Microsoft is not the worst at abandoning things developers have invested in! Not while there's Google around. NET, only to furiously backtrack from the howls of outrage.

#Microsoft silverlight end of life windows 8#

Microsoft almost did it when Silverlight came out and they announced it would be the main development platform for Windows 8 (apps!) eclipsing.

And of course when everyone was roasting me for not moving on back in the day, I reminded them that they'd get the dagger in their back eventually.

#Microsoft silverlight end of life code#

I have code written in the mid 1990's that still runs unmodified on a modern Windows machine. Coming from a DOS background I never used that stuff anyway, going to the file system myself. NET they didn't do it by breaking VB itself, they did it by breaking the tools many VB programmers had been taught to use like data access. When Microsoft tried to boot people off VB into. NET there are obviously parts of Windows and other Microsoft products which clearly remain written in VB, because the VB6 runtime has been part of Windows since Win 2000 and still is in Windows 10. I have only found one bug in the compiler in nearly 20 years of heavy use. I still use it today because it is extremely stable and usefully performant.