Google first announced their plan to deprecate support for Silverlight in their Chrome web browser last year, and they recently reaffirmed this decision with specific timelines. Support for Silverlight inside Chrome will see deprecation starting in January 2015, with workarounds ending in April 2015. The possibilities were (a) Google might push their timelines out; or (b) Microsoft might come with a solution. Before we talk about paths forward and the future, let’s discuss the current facts.
1. Sometime in January 2015, Google will release a version of Chrome that will prompt users to enable Silverlight when accessing a Silverlight application. Once enabled, the setting should stay indefinitely, and the user won’t be asked again. This is very similar to the functionality seen today in Firefox.
2. Following that change, sometime in April 2015, Google will roll out another update that will disable Silverlight from running in Chrome entirely. At this point, it will be technically possible to override this behavior in Chrome’s settings, but the average end user can’t be expected to do this.
3. Finally, sometime around September 2015, Chrome will completely lose the ability to run Silverlight with no way to override.
So in case you have some tools working on Silverlight, web resources in Silverlight in your CRM and you expect it to cross-browser, you will not be able to work through it .
Now the support for other browsers for Silverlight. Referring from Wikipedia:
Refer Microsoft site:
Microsoft Silverlight web resources remain supported in Microsoft Dynamics CRM 2015 and Microsoft Dynamics CRM Online 2015 Update for backwards compatibility. For components that will be able to be presented on all clients, we recommend using HTML web resources with HTML5 instead of Silverlight.
For some, standing up a parallel HTML5 application has taken only hours or a few days; for others it can be more time consuming, depending on the level of customization required. This is the way forward to go.