Strong names and binding redirects

Another important part of the story that we haven’t yet discussed is assembly strong naming. When an assembly has a strong name, the binding to that assembly becomes very strict. That is, if assembly C depends on assembly X 2.0, it’s not going to be happy with any other version of X, even if it’s X 2.0.0.1.

Note: I’m now talking about assembly versions rather than package versions, but let’s assume that they match, as will usually be the case.

Having just started using NuGet and ran into a version compatibility problem with FluentNHibernate and NHibernate 3, this solved my problem.

Just run the Add-BindingRedirect command while having your startup project correct and it auto generates in your app.config.