#HOW TO RUN SILVERLIGHT IN CHROME 47 HOW TO#
#HOW TO RUN SILVERLIGHT IN CHROME 47 INSTALL#
#HOW TO RUN SILVERLIGHT IN CHROME 47 SOFTWARE#

These browsers still support Silverlight content. This issue does not occur in Microsoft Internet Explorer, Mozilla Firefox, or Apple Safari. HTML5 overload at DevConnections 2011, October 31. Д«UILD Day 2 Keynote: What You Need to Know

#HOW TO RUN SILVERLIGHT IN CHROME 47 HOW TO#

How to Pick Your Platform: Silverlight, Metro, or. It's an important part of the measurement (since it's the first HTML5-friendly MSFT browser), but it in no way is the entire measurement.

#HOW TO RUN SILVERLIGHT IN CHROME 47 INSTALL#

HTML5 install base is NOT measured in terms of IE9. Todd Actually, Modernizr is just a simple API for browser 'Feature Checking.' It's not intended to add support for missing features (though it does 'cheat' a little and add some basic HTML element support to older versions of IE).ДЄnd actually, I see I have a typo in my previous comment. Love the flowchart with the decision points.Д¬an't you just use the Modernizr js library to include html5 compatibility for older browsers? I didn't think IE9 adoption was any kind of a requirement. That said, if you don't really need to reach devices (like iOS and Android), Silverlight is still a fair choice.Д®cellent overview. On mobile and devices- even better support. On the desktop- Chrome, Safari, Firefox, IE9/10, Opera (+ polyfills for older browsers). It's measured in terms of all browsers that can process and run HTML5- which is a lot. Todd That's also a fair 'rule of thumb' for picking between Silverlight and HTML5 install base is measured in terms of IE9.

I would probably go for Silverlight, given the trivial install time and good compatibility with WinRT. If I was writing a non-metro non-LOB app for Windows would I go for HTML5? What's the installed based for ie9? I think the installed based for. And for Reach (and not so Rich) apps, ASP.Net is best. I think for Rich (and not so Reach) apps, Silverlight is great. (And, of course, Telerik is already armed with all of the tools you need for today's reality, and we're preparing tools for tomorrow's Metro option.) And reality in a Windows 7 world (that will still work in a Windows 8 world) means Silverlight, WPF, and HTML5.

IF, however, you want to put apps on the Windows Tablets that will start shipping late next year, and IF you accept that these apps will only run in that Windows 8 Metro environment, thenВ you should start digging-in to and learning WinRT.ДЇor everyone else, don't lose sight of reality. That means any project that has as a requirement 'Support Windows 7 clients,' should only be considering WPF, Silverlight, WinForms, and 'web' technologies (HTML/JavaScript + their server-side counterparts, like ASP.NET). These are Windows 8 onlyВ technologies, and there will be no backport layer that will let you run Metro apps on Windows 7. If your answer to this question is 'Yes,' Metro style apps and WinRT should not be on your radar. The first decision is the most important, though: Do you need to continue building apps that work in Windows 7? Clearly, there are many nuances not covered in this tree, but I'll work on expanding the 'logic' to make it more bullet proof in the coming weeks.

In this over-simplified decision tree, I try to provide some crude logic for how to pick between your platform options. In fact, there are a lot scenarios where it's notВ a good choice.

#HOW TO RUN SILVERLIGHT IN CHROME 47 SOFTWARE#

While Windows 8 is ushering in an exciting new model for Windows development called 'Metro style apps' that run a new 'unified' Windows Runtime (WinRT), it's not necessarily the right choice for all new Windows software development.

How to run silverlight in chrome 47