An Interesting List of Development Stuff (April 2014)

ILODS - April

In this month’s installment of the ILODS, we take a look a quite a few announcements that were made at Microsoft’s Build conference, articles to help you figure out if you are over-thinking your development projects or if you are simply blaming the guy that was there before you, the Heartbleed bug, Javascript, open-sourcing, New Orleans and much, much more.

Knowing Too Much to Code

It’s not very often that we associate experience with in inability to get something done, however it may be the case in what Scott Hanselman calls “Analysis Paralysis”. In this blog post, Scott discusses how more experienced developers might “over-think” many sometimes simple applications and make them far more complex than they need to be. He reminds us to ask ourselves “are we going to need that” throughout the development process to help curb this paralysis from affecting our productivity.

From “Potent Potables” to the Human Genome

Although it isn’t directly development-related, it’s always fun to see what development can actually result in. Any fans of Jeopardy should remember the cerebral beat-down served by IBM’s Watson to trivia wizards : Ken Jennings and Brad Rutter (primarily thanks to its insane robot buzzer reflexes). However, it now appears that Watson is now on our side and it’s opponent is a nasty one : cancer.

IBM hopes that Watson will be able to analyze millions of medical records and find correlations between cancer patients that might be impossible for human analysis to discover. Hopefully, this data-first approach may lead to new treatment methods and may help Watson solve one of our generations most challenging questions : finding a cure to cancer.

Extensions. Extensions Everywhere!

In his talk at //Build this yearMads Kristensen discussed the myriad of different tools and extensions available for Visual Studio that can help developers be more productive and in general make their lives easier. The list has extensions that cover a wide variety of topics such as productivity, templating, styling and more. I would highly recommend checking it out to see if you discover anything that makes you say “I’ve been looking for something like that!”.

And the Two Become One : Durandel and Angular Converge!

In this article, Rob Eisenberg (the creator of Durandel) discusses the differences and similarities between Durandel and the popular Angular Javascript frameworks in hopes of providing a response to “Which one should I use?”. He covers an ideal framework that merges many of the stronger features from each framework and how this convergence will help shape the futures of both of the respective libraries.

Change Your Password. Probably. 

One of the largest stories of this month has been the uprising of a nasty bug known as Heartbleed. The Heartbleed bug itself is a vulnerability within the popular OpenSSL cryptographic library and it basically leaves systems using it “exposed” and allows virtually anyone access to any secrets that might be housed behind the normally secure SSL walls if exploited.

If you are unsure if you might need to change your password or if you would like an idea at the popular systems that were affected, you may want to check out this link which details many popular sites to determine if you need to change your password. Additionally, you will want to ensure that you don’t change your password until the affected site has been properly patched and their certificates have been renewed.

Since this is a .NET specific blog, I will note that if you are using IIS then you have nothing to worry about as Microsoft uses schannel to handle all of its SSL needs.

Meet New Orleans.

This has nothing to do with the city in my home state and has everything to do with building highly-scalable Azure based applications. In this article, the ASP.NET team reintroduces project “Orleans”, which provides an approach to building high-scale applications using a service-based model. The project was used heavily within the popular Halo game series to help it achieve its massive scalability needs. It’s openly available currently, so you can head over an visit the project on CodePlex and check out if it may fit the bill for the needs of one of your current or upcoming projects.

Building Javascript Applications like a Superhero!

If you like Javascript and you have a strong desire to build them like a superhero, then this might be just the thing for you. The team at Superhero.js compiled a huge assortment of  resources relating to building and maintaining large-scale Javascript applications, organizing your code and utilizing the appropriate patterns, testing your applications and much, much more.

Introducing IdentityManager

In this post, security guru Brock Allen introduces his most recent creation : IdentityManager, a tool to help manage user identity data through the new ASP.NET Identity or his own MembershipReboot library. IdentityManager provides an extremely easy to use interface that should replace the recently departed ASP.NET Web Site Administration tool that many developers were extremely fond of in Visual Studio 2012. It supports user creation, password changes, e-mail, phone, claims and much, much more.

Passing the Blame.

Shamoon Siddiqui discusses why the latest developer at your company might seem like a wizard when compared to your previous developer. This piece covers a wide array of reasons why developers shouldn’t always be compared to one another or why one shouldn’t be necessarily blamed for decisions that were made at the time (hindsight is 20/20). It’s a solid article for any developer that can often be caught blaming others for their decisions without necessarily knowing what it was like being in their shoes.

The .NET Foundation and Open-Source

Another major announcement at the Build conference was the introduction of the .NET Foundation, a collection of open-source technologies and Microsoft’s development framework. It was established to help foster community involvement, collaboration and development with regards to open-source applications and to help bolster the relationship between Microsoft and the open-source community.

A wide range of Microsoft’s technologies within the .NET stack have already been open-sourced such as ASP.NET MVC, SignalR, Web API and even the powerful Roslyn compiler-as-a-service. If you want to dig around the source and see how some of the technologies were established, visit the link above and dive into the technology of your choice.

Additionally, the entire source of the .NET Framework is available as well that interests you and can be accessed through the Reference Source site here.


Debugging Deeper through Reference Source

Debugging Deepr

A little over a month ago, the ASP.NET team announced several changes and updates to the .NET Reference Source and in this post we are going to discuss how to actually integrate it into Visual Studio so that you can step into the actual .NET Framework source when debugging your applications.

What is Reference Source again?

Reference Source, if you are unfamiliar with it, was a project that Scott Guthrie and his team started back in 2007 in hopes of releasing the .NET Framework source to allow developers to easily reference it (without all kinds of decompilation and mischief) to see what was really going on under the hood. Shortly after that release, the team made a few changes that would allow developers to actually step through the source code which was a major step in a very cool direction.

One of the major difficulties with managing something that is constantly evolving like the .NET Framework is purely the fact that it is “constantly evolving”. Updating documentation usually takes time and with a project of this magnitude, it could simply be something that is “left over until the end” or simply doesn’t get done :

Reference Source circa 2007.

Reference Source circa 2007 via Scott Guthrie

Reference Source Meets Roslyn.

As part of this year’s announcement regarding Reference Source, it was mentioned that it would be joining forces with Microsoft’s latest development wonder, Roslyn.

Roslyn is a managed compiler-as-a-service that has really flipped the script in the .NET world recently. It provides all kinds of wonderful features that were simply not possible in previous years and has already been used not only by Microsoft but in many other arenas such as .NETFiddle, Bing Code Search, Semantic Merge and more. Roslyn was used to help generate a semantic index of the entire .NET Framework source to allow it to be searched through with the greatest of ease.

Currently, .NET 4.5.1 is indexed and readily available on the Reference Source site and the ASP.NET team announced a commitment to keep things updated with each upcoming release as they occur to prevent any stagnation that may have plagued the previous versions of the tool. So you can be relatively sure that whenever you are accessing the latest version of the Reference Source that it should be the latest and greatest. The improvements were not limited to just performance either.

The UI received a very stylish overhaul as well and yield some of the nicest looking documentation that you’ll come across :

The New and Improved Reference Source

The New and Improved Reference Source

Another undocumented feature is the tiny snippets of entertaining comments that you can find scattered throughout the source as well :

An example of one of the many entertaining comments throughout the source.

An example of one of the many entertaining comments throughout the source.

Putting it to Good Use.

Let’s actually put the Reference Source to use along with Visual Studio 2013 and use it to debug an application by not only stepping through our own code, but into the source of the .NET Framework as well.

To get started, there are a few changes we need to make within Visual Studio that will allow us to target the Reference Source (which will primarily consist of enabling and disabling a bunch of properties in the Options menu).

Open up Visual Studio and navigate on over to the options menu (Tools > Options > Debugging > General) as seen below :

You'll need to enable and disable the following options within the Debugging Options in Visual Studio

You’ll need to enable and disable the following options within the Debugging Options in Visual Studio

and then you are going to disable the following options :

  • Just My Code
  • Step over Properties and Operators (Managed Only)
  • Require Source Files to Exactly Match the Original Version

and enable these ones :

  • Enable .NET Framework Source Stepping
  • Enable Source Server Source

After making the changes, your options menu should look like this :

This is what your Debugging Options should look like prior to stepping through Reference Source

This is what your Debugging Options should look like prior to stepping through Reference Source

Then, you’ll need to make sure that when debugging that you are targeting the actual Visual Studio Reference Source. You can do this by visiting the Symbols area under options (Tools > Options > Debugging > Symbols) :

You'll need to access the Symbols area in order to use Reference Source when debugging

You’ll need to access the Symbols area in order to use Reference Source when debugging

From here, you’ll want to target the Reference Source symbols available at You’ll need to click the Add Symbols option within the Symbols area and add the previously mentioned URL :

Click the Folder icon and add the appropriate symbols reference for Reference Source

Click the Folder icon and add the appropriate symbols reference for Reference Source

What I have found to be a safer and more reliable approach however, is to simply download the source and reference it locally from the following location :

After making those changes, you’ll need to ensure that the project that you are going to be debugging is targeting .NET 4.5.1. Debugging through Reference Source is going to currently be limited to 4.5.1 and above since those are the only actual versions of the .NET source that have been indexed so far.

Looking Under the Hood.

Now that we have configured everything, let’s make a really simple program to demonstrate traveling through the source.

// Generate a collection of values (1-100)
var numbers = Enumerable.Range(1, 100);
// Order them randomly
numbers = numbers.OrderBy(n => Guid.NewGuid());
// Store these values in an array
var numberArray = numbers.ToArray();
// Sort the array

Using the simple program above, we will create a collection of numbers, randomly order them, store them in an array and then finally sort them using a variety of methods.

Let’s place a breakpoint on the first line and run the program.

When you hit your first breakpoint, right-click on the method (in this case System.Linq.Enumerable.Range) and you should see an option within the context menu called “Step Into Specific” which will allow you to send the debugger into the .NET source for that particular method as seen below :

You can use the "Step into Specific > (Your Method)" option to debug through the .NET source.

You can use the “Step into Specific > (Your Method)” option to debug through the .NET source.

After selecting the method to step into through “Step into Specific”, you’ll see that the debugger jumps into the related .NET source and you can step through the method as you would expect within any other .NET application being debugged :

After using the "Step into Specific" option, you'll be presented with the source for your specific function, which you can debug as expected.

After using the “Step into Specific” option, you’ll be presented with the source for your specific function, which you can debug as expected.

And that’s basically all you need to know about using Reference Source within Visual Studio to debug your applications. You should be able to jump into any of the assemblies that are currently supported within Reference Source without any issue.


A few other considerations if you are having trouble :

  • Debugging through Reference Source currently ONLY works for full versions of Visual Studio 2013 (sorry no Express versions). I’ve spoken with several members of the Visual Studio team and they are looking into possibly removing this restriction in the future.
  • Ensure that the assembly that you are attempting to step into is one of the available assemblies for debugging mentioned here.

If you still continue to encounter any errors or something isn’t working that you believe should – contact the Reference Source Feedback team via the “Feedback” link on the Reference Source page.

No April Fooling: Officially a Microsoft MVP.


April 1st is a day that is frequently dedicated to pranks, bogus news and tomfoolery.

Generally keeps everyone’s shields of skepticism on high alert and I consider myself to fall into this category. So I have to say that when I received an e-mail from Microsoft with the tagline of “Congratulations 2014 Microsoft MVP!” I was extremely hesitant (I mean what a terrible day to make an announcement on).

April Fools Joke? Nigerian Prince Scam? Or Legit?

April Fools Joke? Nigerian Prince Scam? Or Legit?

As I continued reading through the e-mail, I didn’t find any evidence that might require my bank account information or wire-transferring thousands of dollars to a Nigerian prince. In fact, things were beginning to look legitimate and that I might actually have received the award. A quick tweet to Dora Chan (the North American MVP Lead) quickly confirmed my suspicions and a small amount of celebration went down in my office :

Dora dispelling the possible April Fool's Myth.

Dora dispelling the possible April Fool’s Myth.

I was officially a Microsoft MVP for ASP.NET / IIS and I really couldn’t be more proud.

I’ve become very close with several MVPs primarily through my work in the ASP.NET Forums and I have a great deal of admiration for them. They are extremely smart and passionate people that dedicate days and hours of their lives to helping others learn and become better at what they do. I have looked up to several of these individuals every since I began contributing to the development community and I am extremely honored to be able to join the MVP ranks alongside them.

What the MVP Program Is? (this is primarily for my untechnical family members and friends)

To quote from the program’s page itself for those unfamiliar with the program :

The Microsoft Most Valuable Professional (MVP) Award is our way of saying thank you to exceptional, independent community leaders who share their passion, technical expertise, and real-world knowledge of Microsoft products with others. It is part of Microsoft’s commitment to supporting and enriching technical communities. Even before the rises of the Internet and social media, people have come together to willingly offer their ideas and best practices in technical communities.

How did you end up with one?

The simplest answer to this would revolve around the days (and likely weeks) of time that I spend in discussion groups, blogging, offline activities and contributing to the ASP.NET (and a few other) forums.

I’ve always been a fan of helping others in any ways that I could. My work on the forums has been extremely rewarding and it has yet to become tiresome (even averaging around an hour a day for a year and a half). I’ve met some great people that I can turn to for advice of my own and I’ve been able to mentor many novice developers and help point them in the right direction when they run into issues.

As far as how I actually ended up with the award… I was nominated by several users (some MVPs and some not) that encouraged me to pursue the actual award, believing that I would be a reasonable candidate for it. I was a bit hesitant at first, as I had heard the discussions behind the scenes regarding granting the award itself were extremely rigorous, but I figured “what the hell”.

So after a few months - I entered in all of my pertinent information, clicked send and basically forgot about it.


I am extremely honored to receive this award and it means a ton to me. So I figured I would throw out a handful of thanks since this is my blog and I can “do that” :

  • Thanks to my wife, Katie for putting up for my hours of sitting in bed with my face illuminated from a Surface as I answered questions all night.
  • Thanks to my employer, Structure X for being an awesome place to work for (and more specifically to Blane for being an incredible person to work for).
  • Thanks to my parents, obviously because I wouldn’t be here.
  • Thanks to my alma mater, McNeese State University for having a great Computer Science department that wasn’t actually afraid of Microsoft technologies like C#.
  • Thanks to the ASP.NET Forums and all of the people involved in it (the moderators, the MVPs, the management team and everyone who goes there to either ask questions or answer them).
  • Thanks to the academy, err… wrong speech.
  • Thanks to Microsoft for making a kick-ass platform like .NET that I really enjoy working on and for sending me the e-mail that brought this post about.

Finally, thanks to you, whoever you are, for reading my blog and helping make part of this possible as well. I appreciate you.

An Interesting List of Development Stuff (March 2014)


In this St. Patrick’s day installment of an Interesting List of Development Stuff, we dive into a more .NET-centric approach (with a majority of the topics at least being in the realm of .NET) but as usual, there should be something for everyone. The Roslyn compiler continues to make waves and appears in several of the articles (which we may see as a trend as it continues to grow in popularity) and there’s also a few articles pertaining to games (if that’s your thing).

Depixelizing Pixel Art

Microsoft Research is always doing cool stuff and this article is no exception. It discusses an algorithm that was developed to help smooth the appearance of pixelated images (mostly involving Nintendo-related characters) and it yielded some really neat results. I am sure that nothing excites people more than smooth pixels, but this article has everything : badass-looking video game characters (that we have always wondered what they would look like in their unpixelated glory), legit scholarly work on algorithms, splice curves and more (again decorated with video game characters) and its all packed into 8 pages.

I would highly encourage anyone interested to read through the actual paper itself and if that isn’t your thing, at least take a look at the supplemental material to see it in action.


Brad Wilson and Jim Newkirk of Tier 3 introduce their latest creation ElasticLinq, which is an open-source project that aims at integrating elastic-searching using LINQ syntax within .NET. It’s a tool that was originally developed in-house at Tier 3 to help ease the transition for developers with traditional database backgrounds to NoSQL-based databases and now hopefully it can help you make the transition as well!

How Roslyn and Azure Helped Create .NET Fiddle

I’ll use this as a pseudo-followup to my post last year on .NET Fiddle. .NET Fiddle has really taken off and added all kinds of awesome new features such as NuGet support, MVC support and all kinds the general badassery that one would look for in an online developmental sandbox. This short article isn’t so much about the merits of .NET Fiddle, but more of a look behind the scenes at how it came to be; you can think of it as a love story between Azure and Roslyn.

Open-source Projects! Come on down!

If you are a big fan of open-source software or you have an open-source project, then listen up. features a large listing of available services and APIs that are offered free of charge to open-source projects. They vary in scope but there are a lot of very well known vendors involved – so if your project needs a little extra something and your pockets are light, check it out.

There’s a new operator in town.

It looks like one of the most popular suggestions to appear within Microsoft’s UserVoice system is finally coming to fruition. The Safe Navigator operator (?.) will be likely introduced within the next iteration of C# and Visual Basic and should aid in warding off those NullReferenceExceptions that always find a way into our lives, hearts and applications.

Atom, the completely hackable Editor

The folks at github set the web ablaze with all kinds of chatter and backroom deals when discussion of their Atom editor broke out. Atom was designed as a completely “hackable” editor that could be easily extended to do – really whatever you wanted it to do. It’s still a project that is very early in its infancy, but it is something to keep your eye on.

Meet Reference Source

The great Scott Hanselman discusses another one of the recent offspring from the seemingly promiscuous Roslyn compiler in the form of Reference Source. This incredible innovation will now allow developers to step through the actual source of the .NET Framework while debugging their applications (so if you have ever wondered just what kind of sort was going down in that Array.Sort() method, here is your chance). It’s certainly a tool worth keeping your eye on – and if you want to hear and see more about it, you can check out this post from the MSDN team as well.

Walking through the Code of Games

Fabien Sanglard‘s blog is a fascinating place to visit if you haven’t been by (you can get there by just clicking the link). He has a myriad of different articles, book reviews and discussions on algorithms, but the reason I am bringing it up are his source code reviews. Now, I know that most people would cringe at reading a source code review, but these focus on actual commercial games like Doom, Prince of Persia, Duke Nukem 3D and Fabien does a great job of “skipping to the good parts”.


I’m not saying anything more about this – you’ll likely hate me if you haven’t previously discovered it. It’s digital heroin.

Introducing Bing Code Search, an easy way to find code samples from within Visual Studio 2013

Time is valuable and sometimes taking the time to open up a new browser tab to search for an example of code to do something can be a pain (because we can also be lazy). Thankfully, Microsoft’s Language Experience team created a product just for you: Bing Code Search.


What Does It Do?

Released just this month as an extension for non-Express editions of Visual Studio 2013, Bing Code Search presents some very cool and useful features, which may be especially useful for experienced developers that need a quicker method of accessing examples and resources and for new developers still trying to figure out the code they need to accomplish tasks like reading files or iterating through collections.

After installing the extension in Visual Studio, you’ll see the  a small Bing logo above the native Visual Studio Intellisense. This will allow you to search for and use code examples and snippets from sites like Stack Overflow, MSDN and more without ever leaving your development environment or dragging an open browser onto another monitor :

Using the Bing Code Search to suggest possible solutions to a problem

Using the Bing Code Search to suggest possible solutions to a problem

What is going on here?


Just kidding, but in as with most recent Microsoft innovations in the realm of development, the Roslyn compiler is involved (which is a bit magical). Basically, when you begin your search, your specific query is sent up to Bing along with several other important contextual pieces of information related to your project (such as the Project type, contextual keywords and other goodies) and then it returns a filtered and ranked set of results that might best match the code example you are looking for.

Since there isn’t a holy grail website containing all of the latest a greatest code examples, the code search will actually scour a multitude of different Q/A sites along with some other documentation and resources and compile a listing of relevant code examples that the developer can easily use either for documentation or to copy-paste directly into their project.

How Do I Use It?

The Bing Code Search extension is currently only available for Visual Studio 2013 (non-Express editions) and can be easily downloaded and installed from the Visual Studio gallery at link provided below :

If you don’t have Visual Studio 2013 or you just want to get an idea of how the service works, you can access a fully working example running below at Microsoft Research’s CodeSnippet area :

Try it out.

As a free tool that is incredibly easy to use, I would highly recommend giving it a shot if you have a non-Express edition of Visual Studio 2013 installed. It’s still a very early product and will likely continue to improve in the future (hopefully expanding to non-Express editions as well as earlier versions of Visual Studio), but it may be a great tool to consider adding to your development arsenal either as a time-saver if you are an experienced developer or as an excellent learning tool for those just diving into the development world.

An Interesting List of Development Stuff (February 2014)


In this installment of my monthly treasure trove of development stuff, we take a slightly more .NET-oriented approach by covering several ASP.NET specific topics, resources and more. But there are quite a few other things that may be applicable to just about any kind of developers (and especially those that may be looking for a job).

Send a Valentine’s Day Math-o-Gram

In honor of Valentine’s Day, the folks over at Desmos decided that rather than sending a crummy card to your loved one, you could give them something that all women really love: math. By creating a very simple Node.js application, you can plug in different formulas and create a customizable “love graph” to send to your significant other.. or just play around with it.


No, sadly this is not some new breakfast-related concoction covered with delicious syrup. What is it however is an incredibly useful extension to Visual Studio that adds a bunch of different snippets, templates and other goodies into Visual Studio to help you become a more efficient and productive .NET developer.

Codility Training

Codility is a great site that administers short, automated programming tests for companies that are looking to hire developers. The tests can be performed in a variety of languages and they don’t simply evaluate if the applicant can solve the problem at hand, but how efficient they solved it (considering computational complexity) and if they handled edge cases as well. Now, obviously most readers of this blog are not going to be hiring managers, but Codility offers a free training area to help prepare those that are entering the job market to beef up their problem solving skills. It’s a superb resource for those of you out there that are currently in the job market and want to improve your chops.

Who needs Code Reviews?

A slightly satirical look at the benefits to productivity, developer happiness and deadlines when developers stop working about reviewing code and just start coding.


While it is still just in beta, Strapfork is a new visual editor for developing themes using Twitter’s Bootstrap. It aims to make the entire process of customizing and creating your own themes a cinch by allowing you to adjust every detail from gradients to typography and more. Stay tuned for more!

A Last Look at ASP.NET in 2013 and what to look forward to in 2014!

Jon Galloway covers the good times and the bad times had in 2013 by ASP.NET and how it has grown and continues to develop into a young adult (we are so proud). He reviews over all of the major improvements that have been made in the past year and details what to expect and watch for in 2014.

Do you really need jQuery?

Do you ever wonder if you really need to include that jQuery reference in your project or if there might be another very simple approach that could save you all those delicious kilobytes? Well then this is just the link for you. This site reviews over a bevy of tasks that jQuery typically handles and provides the equivalent code in pure Javascript. It’s a great resource for those that may want to slim down their sites and applications a bit if they are just using jQuery for handling things like AJAX or trivial DOM manipulation.


If you develop .NET applications, then you probably are a fan of NuGet (if not, go read about it and then come back when you are a fan). This site helps you find the best and most popular NuGet packages that you might be missing out on and allows you rank existing packages based on quality, documentation and more. It’s worth checking out if you are looking to incorporate a specific feature or package into your application and there are a ton of different choices out there.

Using the Pomodoro Technique and Trello to Lead a More Efficient Life

A great article by John Sonmez using the Pomodoro technique to help dramatically improve your productivity not only in your career, but also to help organize your life.

IdentityReboot and MembershipReboot

Security guru, Brock Allen introduces two of his major projects which aim to improve the existing ways that ASP.NET handles both Identity and Membership from a security perspective. If you have any qualms about weaknesses within ASP.NET and its built-in security mechanisms, you can be almost assured that Brock has addressed those in these two packages. Even if you aren’t a security expert, the introductions are worthy reads that may interest you enough to use them in the future.

When MVC5, SignalR and NuGet Just Won’t Get Along

This is obviously an exaggeration.

This is obviously an exaggeration.

Sometimes things just blow up.

If you have recently attempted to create a new ASP.NET MVC5 project (or any new Web Project within Visual Studio 2013) and decided that you wanted some of that sweet SignalR magic in your application, then you may have encountered the following error :

An exception of type ‘System.IO.FileLoadException’ occurred in Microsoft.AspNet.SignalR.Core.dll but was not handled in user code.

Additional information: Could not load file or assembly ‘Microsoft.Owin, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35′ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0×80131040)

This can easily be reproduced through the following steps :

  1. Create a new Web Application Project in Visual Studio 2013 that uses built-in Forms Authentication (Individual User Accounts).
  2. Add the SignalR package through NuGet.
  3. Attempt to add the following code to your Startup.cs file :
    public partial class Startup
            public void Configuration(IAppBuilder app)
                // Add SignalR Mappings

If you did everything right, then grab some popcorn because you are about to see this :


Why is this happening to me?

Of all of the things to blame, we are going to choose NuGet for this one.

This is currently a known issue within NuGet. The reason for this is that SignalR and some other binaries are built with a dependency over Microsoft.Owin Version 2.0.0, however the appropriate assembly binding redirects are not occurring. This causes a problem as the latest available version of Microsoft.Owin in the public NuGet feed is greater than 2.0.0.

Okay. But how do I fix it?

There are two options here, which I have each had success with so I’ll start with the easiest approach, installing a specific updated version of Microsoft.Owin (and Microsoft.Owin.Security) and ensuring that you are properly targeting it within your web.config.

You can do this within the following steps :

  • Access the NuGet command-line tool within Visual Studio (accessible under Tools > Library Package Manager > Package Manager Console)
  • Install an updated version of Microsoft.Owin and Microsoft.Owin.Security (2.0.1, 2.1.0, 2.2.0 or any other version) using the following command :
    Install-Package Microsoft.Owin -Version 2.1.0
    Install-Package Microsoft.Owin.Security -Version 2.1.0
  • Ensure that your web.config has the appropriate <bindingRedirect> attributes to target the version you selected as seen below :
       <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
           <!-- Other Assemblies here -->
               <assemblyIdentity name="Microsoft.Owin" publicKeyToken="31bf3856ad364e35" culture="neutral" />
               <!-- Notice this targets -->
               <bindingRedirect oldVersion="" newVersion="" />
               <assemblyIdentity name="Microsoft.Owin.Security" publicKeyToken="31bf3856ad364e35" culture="neutral" />
               <!-- Notice this targets -->
               <bindingRedirect oldVersion="" newVersion="" />

The other longer and seemingly less reliable (in my experience) approach

This method appears to only work if the version of Owin that was installed through NuGet is already greater than one of the dependencies that you already have.

The second option involves creating a Console application and then add the SignalR package to it. Then copy the  bindingRedirects from the app.config file of this application to the web.config file in your previous exception-infested MVC application (as Console applications don’t have this same issue).

You really just need to update the oldVersion and newVersion attributes within the <bindingRedirect> sections for your Microsoft.Owin and Microsoft.Owin assemblies within the <assemblyBinding> section of your web.config from :

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <!-- Other <assemblyBinding> elements for your Project -->
            <assemblyIdentity name="Microsoft.Owin" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="" newVersion="" />
            <assemblyIdentity name="Microsoft.Owin.Security" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="" newVersion="" />

to :

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <!-- Other <assemblyBinding> elements for your Project -->
            <assemblyIdentity name="Microsoft.Owin" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="" newVersion="" />
            <assemblyIdentity name="Microsoft.Owin.Security" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="" newVersion="" />

Or more simply, change the <bindingRedirect> sections for each of your Owin-related assemblies from :

<bindingRedirect oldVersion="" newVersion="" />

to :

<bindingRedirect oldVersion="" newVersion="" />