I had a partial breakthrough on this. While debugging an SL5 app in VS2015
from the local file system, IE11 prompted me to allow untrusted ActiveX
content, which it not done since I migrated to the new PC. This made me
suspicious it was mainly security and/or ActiveX preventing SL5 apps from
running remotely or from the file system, and preventing it silently.

Following some hints I set the IE11 Options > Advanced > Security node >
Check the first two "Allow active content" options. This allowed the SL5
apps to run from the local file system. Partial success!

I spent almost an hour fiddling with the Options > Security > ActiveX
settings, thinking the fix was most like in there, and it probably is, but
sadly there are so many combinations and none of them I tried let me run
remote SL5 apps.

As an experiment I lowered the Trusted Sites level to *Low* security and
put the sites containing theSL5 apps in its list. Bingo! They all run
without prompts.

So I can now debug and run SL5 apps everywhere I need, so long as the
remote ones are in the Trusted Sites list, which is only a small bother. So
it only took 2 weeks of part time research and frustrating experiments to
find these workarounds.

*Greg K*

On 3 March 2016 at 18:01, Preet Sangha <preetsan...@gmail.com> wrote:

> Are there any clues in the process monitor?
> On 3/03/2016 11:34 am, "Greg Keogh" <gfke...@gmail.com> wrote:
>
>> I've tried fiddling with IE11's trusted sites, compatibility settings,
>> different versions of the SDK and runtime, adjusting active plugins,
>> running VS2015 under different accounts, running IE11 under different
>> accounts, creating dummy SL5 projects, adjusting object tag versions,
>> comparing Win8 and Win10 behavior ... and more I can't recall.
>>
>> All I've learned is that there is no problem at all on my old parallel
>> Win8 VM with the same software, and I can run remote SL5 apps when I'm the
>> local Administrator. So there's a small clue about the user account, but I
>> don't know what to make of it yet.
>>
>> *GK*
>>
>> On 2 March 2016 at 18:47, Ian Thomas <il.tho...@outlook.com> wrote:
>>
>>> Can’t suggest much, except: It’s not something as simple as your default
>>> browser on the Windows 10 dev machine being stuck at Edge, not IE11, is it?
>>> Windows 10 recently reverted my default applications to what it wanted
>>> (with a polite notification popup), but after several of those reversions I
>>> took the most drastic control panel remedy for defaults and they’re
>>> sticking again (touch wood).
>>>
>>> The most usual complaint I hear about Silverlight and windows 10 is
>>> getting debugging to work in VS. That’s not a problem for you.
>>>
>>>
>>>
>>> Ian Thomas
>>>
>>> Albert Park, Victoria 3206 Australia
>>>
>>>
>>>
>>> *From:* ozdotnet-boun...@ozdotnet.com [mailto:
>>> ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Greg Keogh
>>> *Sent:* Wednesday, 2 March 2016 5:54 PM
>>> *To:* ozDotNet <ozdotnet@ozdotnet.com>
>>> *Subject:* Silverlight runtime
>>>
>>>
>>>
>>> Folks, I'm probably the only person left in this group writing
>>> Silverlight, but I've got a shocking problem that has been uncrackable in
>>> my spare time for two weeks now.
>>>
>>>
>>>
>>> Since I moved over to my new Win10 dev box and installed the SDK
>>> 5.0.61118.0 and the 64-bit dev runtime 5.1.41212.0 I can develop and debug
>>> Silverlight okay, but if I browse to any page with an app that's not on
>>> localhost I just get the blue logo asking me to install the runtime. So
>>> it's  Catch-22 ... it works on localhost and in VS2015, but not when I
>>> browse elsewhere. I'm completely stumped and all web searches produces
>>> ancient useless suggestions.
>>>
>>>
>>>
>>> I just checked on an old VM running Win8 with the same SDK and runtime
>>> and it doesn't have the problem. Is there something different about Win10
>>> or the latest IE11 that I'm not aware of?!
>>>
>>>
>>>
>>> *Greg K*
>>>
>>
>>

Reply via email to