I’ve been pretty busy in recent months, but I’ve finally released my Ruby on Rails course. This course is geared at existing .NET developers who want to see what Ruby & Rails is like, but don’t want to invest the time to learn either. In this course, we go through just enough ruby to get you going and build a Rails applications as quickly as possible, with as little effort as we can get away with. You’ll leanr just enough to get yourself into trouble.
The best part is, I’ll let you check it out for free! For those who currently do not have a subscription to Pluralsight, I’ll give you a 1-week subscription so you can check out my Ruby on Rails course. Send me an email with your name, twitter and what you normally develop with and I’ll send back a subscription.
Send email to email@example.com
Supplies are limited though!
Using SiteFinity 4 is frustrating because right now it isn’t complete and has many issues. One such issue is adding RadControls to a page will break the site giving a yellow screen of death complaining about an assembly.
Could not load file or assembly ‘Telerik.Web.UI, Version=2010.3.1109.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4′ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0×80131040)
This is because according to Telerik, SiteFinity uses RadControls but they are not in sync with the release of the RadControls package.
The Sitefinity isntaller and project manager come with their own version of the Telerik.Web.UI.dll. The version which was used to build the system. We try to upgrade the controls in the CMS frequently, but sometimes they are not the latest controls released.
The problem you are experiencing is because almost the whole UI of Sitefinity is built using RadControls for ASP.NET Ajax. This means that the Sitefinity assemblies reference the particular version of Telerik.Web.UI.dll which is in the bin of the Stiefinity website. When you have upgraded the controls from the VS dialog you have substituted the assembly with a newer one. To fix the problem you must either revert the assembly to in the bin folder or use a binding redirect.
So to fix the problem, you need to add assemblyBinding to the web.config (which is not right in my opinion).
<probing privatePath="bin;sitefinity\admin\bin" />
The <runtime> node can be put under the <configuration> node in any spot.