It has been a long time since I’ve done any greenfield UI development. Most of my projects over the past several years have involved extending existing Web Forms or ASP.NET MVC apps with some new controls here or there. You can imagine my delight in being able to work on a brand new system with AngularJS as the front-end technology.
I’ve heard a number of good things about AngularJS over the past year or so and have familiarized myself with enough of its core concepts to hold (hopefully) an intelligent conversation about it but this is my first time actually using it on a real project. Given that I still have plenty to learn it didn’t surprise me too much when I encountered my first real roadblock – a recursive directive. (more…)
Today I was trying to run the code for a project I’ve just been assigned to. I’d brought down the code from SVN, built the common libraries, and punched F5. Build succeeded. Before long the browser loaded and the beautiful new UI stared back and virtually begged me to start clicking around. Before I could do anything though Visual Studio rudely interrupted with an unhandled exception dialog. This one looked nasty, particularly since I’d never seen it before: System.Security.VerificationException – Operation could destabilize the runtime…
I found a Stack Overflowquestion about this that pointed to Json.NET as a possible culprit. Sure enough, the source of the exception was Newtonsoft.Json. It seems that Visual Studio Ultimate’s IntelliTrace didn’t like something Json.NET was doing and would throw that exception. The issue is said to be resolved as of release 6 but I haven’t upgraded the assembly yet.
For the time being I’ve added a rule to exclude *Newtonsoft.* from the IntelliTrace modules list as recommended by in the Stack Overflow answer. Since excluding the assembly I haven’t seen the problem again.