There is a simple fix for this. An ASP.NET solution hard-codes the assembly version in the Web.config file. For example, look at a snippet of code in Web.config for our ASP.NET tutorial:
<add assembly="IdeaBlade.Persistence, Version=3.4.0.3, Culture=neutral, PublicKeyToken=287B5094865421C0"/>
<add assembly="IdeaBlade.Persistence.Rdb, Version=3.4.0.3, Culture=neutral, PublicKeyToken=287B5094865421C0"/>
<add assembly="IdeaBlade.Rdb, Version=3.4.0.3, Culture=neutral, PublicKeyToken=287B5094865421C0"/>
<add assembly="IdeaBlade.Util, Version=3.4.0.3, Culture=neutral, PublicKeyToken=287B5094865421C0"/>
<add assembly="IdeaBlade.UI, Version=3.4.0.3, Culture=neutral, PublicKeyToken=287B5094865421C0"/>
<add assembly="IdeaBlade.UI.WinForms, Version=3.4.0.3, Culture=neutral, PublicKeyToken=287B5094865421C0"/>
<add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies>
The fix is easy. Go to Web.config and do a grobal relacement of "3.3.1.1" with "3.4.0.3".