Parser error on hosted web site

[Stephen Bough]

I have been developing a web site using the asp.net ajax controls and have finally got as far as deploying it onto a parallels hosted web site.
However when I try and access any pages with a telerik control on I get this error.

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Unknown server tag 'telerik:RadTabStrip'.

Source Error:

Line 7: TagPrefix="uc3" %> Line 8: <div style="background-color:#D6E5F3;"> Line 9: <telerik:RadTabStrip ID="CreateSchoolTabStrip" runat="server" Skin="Office2007" MultiPageID="CreateSchoolMultipage" Line 10: SelectedIndex="1" CausesValidation="false"> Line 11: <Tabs>

I've checked and the telerik.web.dll file is in the bin/debug directory along with the application dlls, but for some reason is failing to be picked up.
I'm sure this is something obvious about the remote server setup, but I can't seem to find a solution to it.
Any chance you could point me in the right direction here?

Thanks
Steve.

[Sebastian]

Hi Stephen,

Can you please verify that you have a valid reference to the Telerik.Web.UI.dll in your project either:

• through a Register directive in the markup of the page in question
  or
• in the web.config

Thus our controls should be recognized as expected at compile time.

Best regards,
Sebastian
the Telerik team

[Stephen Bough]

I have a register directive in the page in question :

<%@ Register Assembly="Telerik.Web.UI" Namespace="Telerik.Web.UI" TagPrefix="telerik" %><br>

and I have also tried adding it to the web.config file but it doesn't seem to help.

[Sebastian]

Hi Stephen,

Have you confirmed that you have a valid reference to the Telerik.Web.UI.dll in your project either through the /bin folder or the Global Assembly Cache? Also review the information from this topic to ensure that your assembly registration is correct.

Regards,
Sebastian
the Telerik team

[Stephen Bough]

Figured out what the problem was. It turns out in the end that I was using .NET 3.5 but the hosted site only had 2.0 installed. Once I stuck 3.5 on the host machine it all worked fine!
Thanks anyway.