Only about 3 of 100 or so websites I visit regularly are exhibiting this problem, and only in the Modern version of IE, desktop is fine. I logged in with a different user on the same machine and the problem is still there.
Speaking of patent trolling:
"In slapping the Waterloo, Ont.-based company with damages of $147.2 million last month, a jury determined that RIM infringed on patents owned by Mformation, based in Edison, N.J.
Read more: http://www.ctvnews.ca/canada/rim-says-ruling-overturned-in-patent-infringement-case-1.908338#ixzz2xCl2wyIq "
The follow up:
"Research in Motion says a California judge has overturned a ruling on a patent-infringement case involving mobile device management company Mformation Technologies and vacated a US$147.2-million jury award."
I unit test properties via a ViewModel. The unit tests catch if either a change is made on the view model or the property, the counterpart is updated.
An UI interface such as one that allows a user to select a date graphically, it is the UI that prevents non dates from being entered into the property. If dates had to be within a certain range, then you will have to have code that enforces that, and a unit test could throw valid and invalid dates.
So, I don't unit test properties outside of the ViewModel unit tests, unless restrictions apply, as the date example.
Some "properties" are used as commands and are bound in XAML, and are located in the code behind, and I don't unit tests UI code behind.
- - -
Something that might be useful:
A few sites that crash:
They work on the desktop though.
I recently cleaned out files using the Microsoft / Windows utility just prior to when this problem started. Coincidence ?
My current "Silverlight" project for Windows Phone 7 (mango) was mostly developed from only the unit testing environment. Only the Views are developed in a Silverlight project, which are only the XAML markup and code behind. I have a Silverlight project for the other components of the app that simply contain links to the other files.
I'm already ready for the Modern version of my app and have made sure that the code I have written will work when the time comes. There are a few quarks that I have learned how to get around, either #define or write a separate file for the few areas where there are differences.
So in conclusion: Most of my Silverlight app is really .NET as will the Modern version be.
I do want to switch to C++ and DirectX for a future Modern and Windows phone 8 version. I am very rusty at C++, having switched to C# when it first came out.