I read an article this morning that the silverlight.net site was taken down, or more accurately, redirected to the msdn site. I've spent the past year investing in the technology and now I'm looking to be more and more a fool for having done so - I was interested in using Silverlight as my new desktop application technology. It seemed to be a good approach as it would help prepare me for Windows RT.
Frankly, at this point, Microsoft can go die in a flaming vat of Malaria for all I care.
I don't want to use the HTML stack because it's the most poorly constructed flaming pile of dog poop I've ever encountered. Not every application should have to be in the internet - I don't want to have to master a dozen different technologies distributed by a dozen different insecure companies that needlessly iterate products for the sole purpose of incrementing the version number. Getting them to play nice is a nightmare.
At this point I've no idea what I'm supposed to use for desktop applications as my company won't be going to Windows 8 for at least 3 years - if not longer. Microsoft seems intent on pissing away application development in favor of the idiotic consumer market - because we all know we need more content that feature LOLZ CATS.
Why the hell should I embrace Windows RT when it will be replaced by Windows XX or some other nonsense? I'm trying to write business software here - I cannot have a complete ecosystem change every 24 months because when it costs $50K plus to develop software it needs to work for 10+ years to realize a decent ROI. Oh no matter that - I'll port 10,000 man hours of applications to Silverlight, then RT, then ??, then ??, then ?? over the course of 9 months while picking up a dozen new ways of doing things. No problem - we can afford a staff of 200 people to keep up with it.
*checks the want ads for a opportunties to work as a dish washer*
Missed this, did you? I haven't created a Windows Store app, but from what I understand you can create on in C# that has a UI based on XAML. No HTML need be involved.
True, it won't work on Windows 7. However, Silverlight should be able to run on Windows 8 (the desktop version).
Also, if you create a "portable class library", that project should work in Silverlight/WinRT. Then it'd really only be the XAML portion you'd have to duplicate across a one Silverlight and one WinRT project, supposing you want to develop the application on both platforms in parallel. The solution would look like this:
Portable Class Library (contains business logic, utility classes, interfaces, and so on)
Silverlight Project (contains Silverlight UI, mostly in XAML)
Windows Store XAML App (contains WinRT UI, mostly in XAML)