Hi Adam,
I understand how this happened in retrospect but did not anticipate it ahead of time. I prepare the deployment files packages mainly with the intent that they work in production environments, though I do realize that people do try to use them also in Visual Studio and I try to avoid problems with use in VS. What happened was a few minor bugs were reported in the few days after the release and I patched the release with a new version of mojoPortal.Web.dll and maybe a few other files but not mojoPortal.Business.dll as it had no changes. While this works fine in production environments, I guess in VS the dlls may know that they were compiled against a different build of a dll than the one in the bin even if it had no changes. In the future I will keep that in mind and try to always deploy all the dlls even if they have not changed when patching one of them.
I hope to make a new release with a few bug fixes tomorrow or the next day.
Best,
Joe