Hi,
I am using the ImageManager in a RadEditor and wanted to remove the path at the top of the file area - what I believe is called the AddressBox. I found instructions on your site and copied the EditDialogs folder and its content to my project.
I modified FileBrowser.ascx and specified VisibleControls="Grid,TreeView,ContextMenus,Toolbar" for the RadFileExplorer (i.e., excluded the AddressBox).
When I try to build my solution I get the following 2 errors at lines 1771 thru 1780 in StyleBuilder.ascx:
Error 204 'Telerik.Web.UI.Editor.ColorPicker' does not contain a definition for 'ClientIDMode' and no extension method 'ClientIDMode' accepting a first argument of type 'Telerik.Web.UI.Editor.ColorPicker' could be found (are you missing a using directive or an assembly reference?) C:\Visual Studio 2010 Jim\Projects\ITOptimizerNewDev\ITOptimizerWeb\StyleBuilder.ascx 1771
Error 205 The type or namespace name 'ClientIDMode' does not exist in the namespace 'System.Web.UI' (are you missing an assembly reference?) C:\Visual Studio 2010 Jim\Projects\ITOptimizerNewDev\ITOptimizerWeb\StyleBuilder.ascx 1771
If I remove the ClientIDMode="Static" from the 4 statements that include it, the build completes successfully and I get the result I was looking for - no AddressBox.
Any idea how to address these errors?
Thanks
Jim
I am using the ImageManager in a RadEditor and wanted to remove the path at the top of the file area - what I believe is called the AddressBox. I found instructions on your site and copied the EditDialogs folder and its content to my project.
I modified FileBrowser.ascx and specified VisibleControls="Grid,TreeView,ContextMenus,Toolbar" for the RadFileExplorer (i.e., excluded the AddressBox).
When I try to build my solution I get the following 2 errors at lines 1771 thru 1780 in StyleBuilder.ascx:
Error 204 'Telerik.Web.UI.Editor.ColorPicker' does not contain a definition for 'ClientIDMode' and no extension method 'ClientIDMode' accepting a first argument of type 'Telerik.Web.UI.Editor.ColorPicker' could be found (are you missing a using directive or an assembly reference?) C:\Visual Studio 2010 Jim\Projects\ITOptimizerNewDev\ITOptimizerWeb\StyleBuilder.ascx 1771
Error 205 The type or namespace name 'ClientIDMode' does not exist in the namespace 'System.Web.UI' (are you missing an assembly reference?) C:\Visual Studio 2010 Jim\Projects\ITOptimizerNewDev\ITOptimizerWeb\StyleBuilder.ascx 1771
If I remove the ClientIDMode="Static" from the 4 statements that include it, the build completes successfully and I get the result I was looking for - no AddressBox.
Any idea how to address these errors?
Thanks
Jim
2 Answers, 1 is accepted
0
Hi Jim,
By design RadFileExplorer (and RadControls in general) supports only ClientIdMode="AutoID" and it is highly recommended to configure it this way in order to generate correct client IDs.
This is done because the whole implementation of the RadControls is based on the client IDs which are being generated in order to find and work with them (and respectively with the child controls with such Client IDs).
Greetings,
Veselina
the Telerik team
By design RadFileExplorer (and RadControls in general) supports only ClientIdMode="AutoID" and it is highly recommended to configure it this way in order to generate correct client IDs.
This is done because the whole implementation of the RadControls is based on the client IDs which are being generated in order to find and work with them (and respectively with the child controls with such Client IDs).
Greetings,
Veselina
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
0
Jon
Top achievements
Rank 1
Rank 1
answered on 27 Dec 2012, 07:02 PM
Veselina,
This answer does not make sense to me. When I migrated from VS2008 to VS2010, I encountered the same set of errors, and found that I could resolve this by changing my web site's .NET version to 4.0.
So far I have not had to make any code changes.
-Jon
This answer does not make sense to me. When I migrated from VS2008 to VS2010, I encountered the same set of errors, and found that I could resolve this by changing my web site's .NET version to 4.0.
So far I have not had to make any code changes.
-Jon