- The Windows Store WebView object does not allow you to ignore script errors the way older iterations of the control did for traditional C# Windows apps
- This bug showed up even after compiling and building in release mode
- Every time I found a place where this question had been asked previously, there was no consistent answer on what was causing the problems.
I tried several fixes, but even setting breakpoints did nothing – every time I ran into a website that had scripting errors, my app was toast. It wasn’t until I found a post on Stack Overflow that took over six months to be answered that I discovered it was being caused by my settings in Visual Studio’s debugger.
Just goes to show that we’re always learning. I wish I understood a little more about what it was that was behind all of it – I can’t really understand why VS would attach a separate debugger to an executable that was already in the debug process. An adventure in application development to be sure.