farmkasce.blogg.se

1. MICROSOFT SILVERLIGHT FOR MAC NOT WORKING MAC OS X
2. MICROSOFT SILVERLIGHT FOR MAC NOT WORKING INSTALL
3. MICROSOFT SILVERLIGHT FOR MAC NOT WORKING WINDOWS

I just want to know how this can be smoothed out, and who to call to make things happen. Please just do not resort to passionate bashing of corporate entities, as that is pointless. Theories, speculations, insider insights and other types of input are welcomed!

MICROSOFT SILVERLIGHT FOR MAC NOT WORKING MAC OS X

Is Mac OS X 10.8.2 simply buggy or generally unstable? Are there other apps that just crash on Mountain Lion? What has to be done to avoid that - has Apple deprecated some API calls? Is this going to end up being just some sort of permissions issue? That was rhetorical.)ĭid Microsoft test Silverlight on an older version of Mac OS X only to have Apple change something in the next revision of Mac OS X?Īre my customers and other people on the Internet doing something unsupportable like run 3rd party utilities that are corrupting the Silverlight installation process? Why can't Apple and Microsoft play nicely, at least in a particular instance where interoperability was showcased and marketed as something that could be relied upon to just work. The entire point of having made an application in Silverlight in the first place, for many decision makers, would have been so that it will be able to be run on a Mac.

MICROSOFT SILVERLIGHT FOR MAC NOT WORKING WINDOWS

Is there a subtext that it is really only supported on Windows though? Microsoft has stated that they plan to support Silverlight through 2021. Who is at fault on this? Apple or Microsoft? Both? Neither? Anyone have any insight into the reasons behind this? Does Silverlight work fine for you on your Mac OS X 10.8.2 machine? I just want to know what gives rise to issues like this? Is it that Microsoft is not consistently testing Silverlight well whenever Mac comes out with a new version of the Mac OS X, or would it be more likely that Apple is specifically trying to subvert Microsoft Silverlight (and other programs apparently) on purpose for some reason? There are apparently a lot of random crashes happening on Mac OS X 10.8.2, with Microsoft Office, and other non-Microsoft applications. People having problems with Netflix on Macs, and problems where a program called MacKeeper messes up the Silverlight installation. There are lots of supposedly "miraculous" solutions, but it doesn't seem to be right that end users would have to jump through hoops to get this to work. There is a lot of evidence on the Internet that many people have been having this same kind of problem. Our app also runs as expected on that Mac machine. I have a Mac that runs Silverlight 5 perfectly but it is a Mac OS X 10.6.8 machine (Snow Leopard). The customers who seem to be having the most trouble are using Mac OS X 10.8.2 (the latest Mountain Lion) Also, our Silverlight 5 app does not start up on that machine.

Google has no plans to change this decision and FireFox is likely to follow this decision, some time in 2016.I have customers who are showing me Mac OS X core dumps that show calls being made to the Mac OS X that cause a Signal Abort (SIGABRT), upon opening the default Silverlight preferences on the Mac. So, from Chrome 45 onwards, it is no longer possible to run Silverlight in Chrome. Silverlight content to access a Silverlight page. On Chrome version 45 or a later version of Chrome, there is no

MICROSOFT SILVERLIGHT FOR MAC NOT WORKING INSTALL

Or that the Install Microsoft Silverlight badge is displayed. That runs Microsoft Silverlight, you see that some content is missing When you use Google Chrome (version 42.0 or later) to access a website

It is no longer possible to run Silverlight (or any other plug-ins that rely on NPAPI) in Chrome. NPAPI was completely removed from Chrome in version 45 released on Sept. In other words, Chrome will likely never support Silverlight again. I think you can take that to mean that Microsoft has no intention of creating a new Silverlight plugin for Chrome that does not rely on NPAPI. I have read elsewhere (see this article by Chris Merriman) that Microsoft's response was that there are other Silverlight capable browser alternatives to Chrome. This is only a temporary solution, however, as they plan on removing that option entirely by, I believe, September. Once you do that, the Silverlight plugin will be available again in the plugins section (along with many other plugins). At the moment they have just disabled NPAPI, You can reenable it by:Įntering chrome://flags/#enable-npapi in Chrome's address bar

Rather, Chrome no longer supports the underlying protocol that Silverlight relies on, NPAPI.