This is a migrated thread and some comments may be shown as answers.

[Solved] Treeview, Sharepoint and ScriptManager

2 Answers 146 Views
TreeView
This is a migrated thread and some comments may be shown as answers.
Krister Klaussen
Top achievements
Rank 1
Krister Klaussen asked on 01 Feb 2010, 07:56 AM
Hi,

I've been developning a custom webpart for sharepoint using the Telerik TreeView control. In my development and test enviroments i have registerd the scriptmanager by adding it to the testpage/aspx-page. This works like a charm.
Then it was time for delpoyment on the production servers, and this is where the problems begin. In the masterpage of the production enviroment i have a scriptmanager. The Page where i add the new custom webpart, use this masterpage. But still i get an error sayin there is no scriptmanager on the page.
Trying for the quick-fix i add a scriptmanager directly to the page im adding the new webpart to. But no sigar, I get a error saying that i can only have 1 scriptmanager pr page.
So the problem is... I cant get the only one scriptmanager that i need to get the webpart going. And i cant remove the scriptmanager on the masterpage, as this is in use on numerous other pages in the portal.
What to do? and why is this happening?

Some practical information:
Treeview added in CreateChildControls event.
Have tried the useless SafeScriptManager from Microsoft SPG

Regards
Krister A Klaussen

2 Answers, 1 is accepted

Sort by
0
Dimitar Milushev
Telerik team
answered on 04 Feb 2010, 08:57 AM
Hi Krister,

Have you tried the instructions we have provided for creating WebParts that use RadControls? I believe they should help.

Regards,
Dimitar Milushev
the Telerik team

Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Follow the status of features or bugs in PITS and vote for them to affect their priority.
0
Accepted
Krister Klaussen
Top achievements
Rank 1
answered on 04 Feb 2010, 10:32 AM
I have found the solution to this one at last. The problem was, as it turned out, that the webconfig in our production environment was referencing 1.0 version of system.web.extensions. After a upgrade everything fell into place and it all started working. I find it kind of ridiculous that there was no better error message giving me clues to what the problem really was.

So everything turnes out ok in the end. Thx for the comeback thou.

Regards
Krister
Tags
TreeView
Asked by
Krister Klaussen
Top achievements
Rank 1
Answers by
Dimitar Milushev
Telerik team
Krister Klaussen
Top achievements
Rank 1
Share this question
or