As it turns out, I did the very silly thing of glossing over an extremely important step in the WebSharper documentation! The problems were caused entirely by me not making sure that my Nuget install was up to date!

So, if your builds have these symptoms, I would suggest updating Nuget.

One last detail; after fixing the Nuget issue, I still had unbound references in new WebSharper projects. This is simply solved by unloading and reloading the new solution in VS2012.

Sorry for the silly mistake on my part, all!

By on 2/13/2014 5:54 PM ()

Sorry about that Bryan. Feel free to also use the tracker - [link:bitbucket.org] this gets our immediate attention. Yes, unbound reference issue is something that I am hoping NuGet/VS will solve, it has been reported to them.

By on 2/21/2014 11:00 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper