diff --git a/README.md b/README.md index ca2693373b..c44682d369 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ --- title: Telerik® UI for ASP.NET AJAX Documentation Repo -publish: false +published: false --- # Telerik® UI for ASP.NET AJAX Documentation diff --git a/_templates/common/wai-aria-templates.md b/_templates/common/wai-aria-templates.md index 03ddacff7f..35366eaf77 100644 --- a/_templates/common/wai-aria-templates.md +++ b/_templates/common/wai-aria-templates.md @@ -1,4 +1,4 @@ -#intro-base +#intro-base This article demonstrates how to enable and use the WAI-ARIA support of the #end @@ -8,4 +8,4 @@ This article demonstrates how to enable and use the WAI-ARIA support of the #intro-two-controls @[template](/_templates/common/wai-aria-templates.md#intro-base) **@{control1}** and **@{control2}** controls. -#end \ No newline at end of file +#end diff --git a/all-pages.md b/all-pages.md index 0f3eec759c..fff9b84b4a 100644 --- a/all-pages.md +++ b/all-pages.md @@ -1,5 +1,5 @@ --- -publish: false +published: false layout: null --- diff --git a/api/client/Telerik.Web.UI.RibbonBarTab.md b/api/client/Telerik.Web.UI.RibbonBarTab.md index 7ed3bb22e9..f2af0447a8 100644 --- a/api/client/Telerik.Web.UI.RibbonBarTab.md +++ b/api/client/Telerik.Web.UI.RibbonBarTab.md @@ -174,7 +174,7 @@ Gets the hierarchical index inside the parent RadRibbonBar ### get_labelElement -Returns the DOM element containing the Tab's text element. +Returns the <a> DOM element containing the Tab's text element. #### Parameters diff --git a/api/client/args/Telerik.Web.UI.RibbonBarMaximizedEventArgs.md b/api/client/args/Telerik.Web.UI.RibbonBarMaximizedEventArgs.md index 3779b0efb4..a9e018d304 100644 --- a/api/client/args/Telerik.Web.UI.RibbonBarMaximizedEventArgs.md +++ b/api/client/args/Telerik.Web.UI.RibbonBarMaximizedEventArgs.md @@ -1,7 +1,7 @@ --- -title: Telerik.Web.UI.RibbonBarMaximizеdEventArgs +title: Telerik.Web.UI.RibbonBarMaximizedEventArgs description: Client-side API Reference -slug: Telerik.Web.UI.RibbonBarMaximizеdEventArgs +slug: Telerik.Web.UI.RibbonBarMaximizedEventArgs --- # Telerik.Web.UI.RibbonBarMaximizеdEventArgs @@ -9,7 +9,7 @@ slug: Telerik.Web.UI.RibbonBarMaximizеdEventArgs Inheritance Hierarchy -* [Telerik.Web.UI.RibbonBarMaximizеdEventArgs]({%slug Telerik.Web.UI.RibbonBarMaximizеdEventArgs%}) +* [Telerik.Web.UI.RibbonBarMaximizеdEventArgs]({%slug Telerik.Web.UI.RibbonBarMaximizedEventArgs%}) Methods diff --git a/api/server/Telerik.Web.UI.Calendar/DatePickerClientEvents.md b/api/server/Telerik.Web.UI.Calendar/DatePickerClientEvents.md index 94773e1f21..34c2e46372 100644 --- a/api/server/Telerik.Web.UI.Calendar/DatePickerClientEvents.md +++ b/api/server/Telerik.Web.UI.Calendar/DatePickerClientEvents.md @@ -31,7 +31,17 @@ Gets or sets the name of the client-side event handler that is executed prior to There can be some conditions you do want not to close the calendar popup on click over it. Then you should cancel the event either by return false; or set its argument args.CancelClose = true; - + +````ASP.NET + + + + +```` ### OnPopupOpening `String` @@ -40,12 +50,34 @@ Gets or sets the name of the client-side event handler that is executed prior to #### Remarks There can be some conditions you do want not to open the calendar popup on - click of the popup button. Then you should cancel the event either by return - false; or set its argument args.CancelOpen = true; - - Set the args.CancelSynchronize = true; to override the default - DatePicker behavior of synchronizing the date in the DateInput and Calendar - controls. This is useful for focusing the Calendar control on a date different from - the DateInput one. - +click of the popup button. Then you should cancel the event either by return +false; or set its argument args.CancelOpen = true; + + +````ASP.NET + + + +```` + +Set the args.CancelSynchronize = true; to override the default +DatePicker behavior of synchronizing the date in the DateInput and Calendar +controls. This is useful for focusing the Calendar control on a date different from +the DateInput one. + +````ASP.NET + + + + +```` diff --git a/api/server/Telerik.Web.UI.Calendar/DateRangePickerClientEvents.md b/api/server/Telerik.Web.UI.Calendar/DateRangePickerClientEvents.md index 4a7c9a21fb..84f62d87eb 100644 --- a/api/server/Telerik.Web.UI.Calendar/DateRangePickerClientEvents.md +++ b/api/server/Telerik.Web.UI.Calendar/DateRangePickerClientEvents.md @@ -29,9 +29,18 @@ Gets or sets the name of the client-side event handler that is executed prior to #### Remarks There can be some conditions you do want not to close the calendar popup on - click over it. Then you should cancel the event either by return false; or - set its argument args.CancelClose = true; - +click over it. Then you should cancel the event either by return false; or +set its argument args.CancelClose = true; +````ASPX + + + + +```` ### OnPopupOpening `String` @@ -42,10 +51,31 @@ Gets or sets the name of the client-side event handler that is executed prior to There can be some conditions you do want not to open the calendar popup on click of the popup button. Then you should cancel the event either by return false; or set its argument args.CancelOpen = true; - - Set the args.CancelSynchronize = true; to override the default - DatePicker behavior of synchronizing the date in the DateInput and Calendar - controls. This is useful for focusing the Calendar control on a date different from - the DateInput one. - +````ASPX + + + + +```` + +Set the args.CancelSynchronize = true; to override the default +DatePicker behavior of synchronizing the date in the DateInput and Calendar +controls. This is useful for focusing the Calendar control on a date different from +the DateInput one. + +````ASPX + + + + +```` diff --git a/api/server/Telerik.Web.UI.Calendar/MonthYearPickerClientEvents.md b/api/server/Telerik.Web.UI.Calendar/MonthYearPickerClientEvents.md index d10bcaf387..8ccf8baf89 100644 --- a/api/server/Telerik.Web.UI.Calendar/MonthYearPickerClientEvents.md +++ b/api/server/Telerik.Web.UI.Calendar/MonthYearPickerClientEvents.md @@ -33,10 +33,18 @@ Gets or sets the name of the client-side event handler that is executed prior to #### Remarks There can be some conditions you do want not to close the calendar popup on - click over it. Then you should cancel the event either by return false; or - set its argument args.CancelClose = true; - - +click over it. Then you should cancel the event either by return false; or +set its argument args.CancelClose = true; +````ASPX + + + + +```` ### OnPopupOpening `String` Gets or sets the name of the client-side event handler that is executed prior to @@ -46,12 +54,31 @@ Gets or sets the name of the client-side event handler that is executed prior to There can be some conditions you do want not to open the calendar popup on click of the popup button. Then you should cancel the event either by return false; or set its argument args.CancelOpen = true; - - Set the args.CancelSynchronize = true; to override the default - DatePicker behavior of synchronizing the date in the DateInput and Calendar - controls. This is useful for focusing the Calendar control on a date different from - the DateInput one. - +````ASPX + + + + +```` +Set the args.CancelSynchronize = true; to override the default +DatePicker behavior of synchronizing the date in the DateInput and Calendar +controls. This is useful for focusing the Calendar control on a date different from +the DateInput one. +````ASPX + + + + +```` ### OnViewChanged `String` diff --git a/api/server/Telerik.Web.UI/GridClientEvents.md b/api/server/Telerik.Web.UI/GridClientEvents.md index da811b7277..2567ee1541 100644 --- a/api/server/Telerik.Web.UI/GridClientEvents.md +++ b/api/server/Telerik.Web.UI/GridClientEvents.md @@ -75,36 +75,44 @@ Gets or sets a client-side event which helps in custom implementation of the bat This client-side event is after a column cell is deselected client-side. #### Remarks -This event is fired after a column cell has been deselected client-side.Fired byRadGridArgumentsN/ACan be canceledNoExamplesascx/aspxfunction - CellDeselected(){alert("Cell deselected!");} +This event is fired after a column cell has been deselected client-side.Fired by RadGrid. +````ASPX + + +```` ### OnCellDeselecting `String` This client-side event is before a column cell is deselected client-side. #### Remarks -This event is fired before a column cell has been deselected client-side.Fired byRadGridArgumentsN/ACan be canceledYesExamplesascx/aspxfunction - CellDeselecting(){alert("Cell deselecting!");} +This event is fired before a column cell has been deselected client-side.Fired by RadGrid. +````ASPX + + +```` ### OnCellSelected `String` This client-side event is after a column cell is selected client-side. #### Remarks -This event is fired after a column cell is selected client-side.Fired byRadGridArgumentsN/ACan be canceledNoExamplesascx/aspxfunction - CellSelected(){alert("Cell selected!");} +This event is fired after a column cell is selected client-side.Fired by RadGrid +````ASPX + + +```` ### OnCellSelecting `String` This client-side event is fired before a column cell is selected client-side. #### Remarks -This event is fired before a column cell is selected client-side.Fired byRadGridArgumentsN/ACan be canceledYesExamplesascx/aspxfunction - CellSelecting(){alert("Selecting column cell!");} +This event is fired before a column cell is selected client-side.Fired by RadGrid. +````ASPX + + +```` ### OnColumnClick `String` @@ -120,9 +128,11 @@ This client-side event is fired after a column available at client-side is created. #### Remarks -This event is fired after a column available at client-side is created.Fired byRadGridTableArgumentsRadGridTableColumn objectCan be canceledNoExamplesascx/aspxfunction - ColumnCreated(columnObject){alert("Column with Index: " + columnObject.Index + " was created");} +This event is fired after a column available at client-side is created.Fired by RadGridTable +````ASPX + + +```` ### OnColumnCreating `String` @@ -130,9 +140,11 @@ This client-side event is fired before column available at client-side creation. #### Remarks -This event is fired before column available at client-side creation.Fired byRadGridTableArgumentsN/ACan be canceledNoExamplesascx/aspxfunction - ColumnCreating(){alert("Creating column);} +This event is fired before column available at client-side creation.Fired by RadGridTable. +````ASPX + + +```` ### OnColumnDblClick `String` @@ -143,9 +155,11 @@ Gets or sets the client-side event which will be fired when a column have been d This client-side event is fired when a column object is destroyed. #### Remarks -This event is fired when a column object is destroyed.Fired byRadGridTableArgumentsN/ACan be canceledNoExamplesascx/aspxfunction - ColumnDestroying(){alert("Destroing column with Index: " + this.Index);} +This event is fired when a column object is destroyed.Fired by RadGridTable. +````ASPX + + +```` ### OnColumnHidden `String` @@ -188,11 +202,15 @@ Gets or sets the client-side event which will be fired when a column have been r This client-side event is fired before a column is resized. #### Remarks -This event is fired before a column is resized.Fired byRadGridTableArgumentscolumnIndex, columnWidthCan be canceledYes, return false to cancelExamplesascx/aspxfunction - ColumnResizing(columnIndex, columnWidth){alert("Resizng column with Index: " + columnIndex + ", width: " + - columnWidth);}ORfunction - ColumnResizing(columnIndex, columnWidth){return false; //cancel ColumnResizing event} +This event is fired before a column is resized.Fired by RadGridTable. +````ASPX + + +```` ### OnColumnShowing `String` @@ -239,17 +257,22 @@ Gets or sets the client-side event which will be fired before the filter menu is This client-side event is fired after the grid is created. #### Remarks -This event is fired after the grid is created.Fired byRadGridArgumentsN/ACan be canceledNoExamplesascx/aspxfunction GridCreated(){alert("Grid with ClientID: " + this.ClientID + " was created");} +This event is fired after the grid is created.Fired by RadGrid. +````ASPX + + +```` ### OnGridCreating `String` This client-side event is fired before grid creation. #### Remarks -This event is fired before grid creation.Fired byRadGridArgumentsN/ACan be canceledNoExamplesascx/aspxfunction - GridCreating(){alert("Creting grid with ClientID: " + this.ClientID);} +This event is fired before grid creation.Fired by RadGridArguments. +````ASPX + + +```` ### OnGridDestroying `String` @@ -257,11 +280,11 @@ This client-side event is fired when RadGrid object is destroyed, i.e. on each window.onunload #### Remarks -This event is fired when RadGrid object is destroyed, i.e. on each - window.onunloadFired byRadGridArgumentsN/ACan be canceledNoExamplesascx/aspxfunction - GridDestroying(){alert("Destroying grid with ClientID: " + this.ClientID);} - +This event is fired when RadGrid object is destroyed, i.e. on each window.onunload. Fired by RadGridArguments +````ASPX + + +```` ### OnGroupCollapsed `String` Gets or sets the client-side event which is fired after a group have been collapsed. @@ -308,18 +331,23 @@ Gets or sets the client-side event which will be fired when the grid is foused a This client-side event is fired after the MasterTableView is created. #### Remarks -This event is fired after the MasterTableView is created.Fired byRadGridArgumentsN/ACan be canceledNoExamplesascx/aspxfunction - MasterTableViewCreated(){alert("MasterTableView was created");} +This event is fired after the MasterTableView is created.Fired by RadGridArguments +````ASPX + + +```` + ### OnMasterTableViewCreating `String` This client-side event is fired before the MasterTableView is created. #### Remarks -This event is fired before the MasterTableView is created.Fired byRadGridArgumentsN/ACan be canceledNoExamplesascx/aspxfunction - MasterTableViewCreating(){alert("Creating MasterTableView");} +This event is fired before the MasterTableView is created.Fired by RadGrid. +````ASPX + + +```` ### OnPopUpShowing `String` @@ -445,28 +473,33 @@ Gets or sets the client-side event which will be fired when is scrolled. This client-side event is fired after the table is created. #### Remarks -This event is fired after the table is created.Fired byRadGridArgumentsRadGridTable ObjectCan be canceledNoExamplesascx/aspxfunction - TableCreated(tableObject){alert("DetailTable with ClientID: " + tableObject.ClientID + " was - created");} +This event is fired after the table is created. Fired by RadGrid. +````ASPX + + +```` ### OnTableCreating `String` This client-side event is fired before table creation. #### Remarks -This event is fired before table creation.Fired byRadGridArgumentsN/ACan be canceledNoExamplesascx/aspxfunction - TableCreating(){alert("Creating DetailTable");} +This event is fired before table creation.Fired by RadGrid. +````ASPX + + +```` ### OnTableDestroying `String` This client-side event is fired when table object is destroyed. #### Remarks -This event is fired when table object is destroyed.Fired byRadGridArgumentsN/ACan be canceledNoExamplesascx/aspxfunction - TableDestroying(){alert("Destroing DetailTable with ClientID: " + this.ClientID);} +This event is fired when table object is destroyed. Fired by RadGrid. +````ASPX + + +```` ### OnUserAction `String` diff --git a/api/server/Telerik.Web.UI/GridTableView.md b/api/server/Telerik.Web.UI/GridTableView.md index cd081884c3..2d1e8a45ae 100644 --- a/api/server/Telerik.Web.UI/GridTableView.md +++ b/api/server/Telerik.Web.UI/GridTableView.md @@ -199,7 +199,7 @@ Use the AlternatingItemStyle property to control the GridTableView control in the form Property-Subproperty, where Subproperty is a property of the GridTableItemStyle object (for example, - AlternatingItemStyle-ForeColor).Nest an element between the opening and + AlternatingItemStyle-ForeColor).Nest an `` element between the opening and closing tags of the GridTableView control.The properties can also be set programmatically in the form Property.Subproperty (for example, AlternatingItemStyle.ForeColor). Common settings usually include a custom @@ -263,25 +263,30 @@ Gets all items among the hierarchy of ### ClientDataKeyNames `String[]` This property is used to specify the field from the underlying datasource, - which will populate the ClientDataKeyNames collection. - This collection can later be accessed on the client, to get the key - value(s).The following example demonstrates the extraction of the data key value for a - given data table view object: - - - The logic is placed in the OnHierarchyExpanded client side event handler, - which is triggered when the user expands a node - in a hierarchical grid, but can be used in any other event, given that a proper - reference to the client table view object is obtained. +which will populate the ClientDataKeyNames collection. +This collection can later be accessed on the client, to get the key +value(s).The following example demonstrates the extraction of the data key value for a +given data table view object: + +````ASPX + + + + +```` + + +The logic is placed in the OnHierarchyExpanded client side event handler, +which is triggered when the user expands a node +in a hierarchical grid, but can be used in any other event, given that a proper +reference to the client table view object is obtained. ### ClientID `String` @@ -492,7 +497,7 @@ Use the EditItemStyle property to control the appearance of GridTableView control in the form Property-Subproperty, where Subproperty is a property of the GridTableItemStyle object (for example, - EditItemStyle-ForeColor).Nest an element between the + EditItemStyle-ForeColor).Nest an `` element between the opening and closing tags of the GridTableView control.The properties can also be set programmatically in the form Property.Subproperty (for example, EditItemStyle.ForeColor). Common settings usually include a custom @@ -513,11 +518,11 @@ There are two possible values defined by the GridEditMode enumeration:InPlaceEditFormsTo display the grid column editors inline when switching grid item in edit mode (see the screenshot below), you simply need to change the EditMode property to InPlace. - To display the grid column editors in auto-generated form when switching grid + ``To display the grid column editors in auto-generated form when switching grid item in edit mode (see the screenshot below), you simply need to change the MasterTableView EditMode property to EditForms. - + `` ### EnableColumnsViewState `Boolean` @@ -641,7 +646,7 @@ Note that the correctness of the expressions in the collection is Gets or sets the group footer ItemTemplate. -### GroupHeaderFooterIndexMap `Dictionary`2` +### GroupHeaderFooterIndexMap ```Dictionary`2``` Returns a Dictionary of group header index and the corresponsding group footer item @@ -661,12 +666,12 @@ Specifies where the grouping will be handled. There are two options:Server-side #### Remarks GridTableView.GroupLoadMode.ServerThis is the default behavior. Groups are expanded after postback to the server for example: - GridTableView.GroupLoadMode.ClientGroups will be + ``GridTableView.GroupLoadMode.ClientGroups will be expanded client-side and no postback will be performed. - + `` and set the client setting AllowGroupExpandCollapse to true: - + `` ### GroupsDefaultExpanded `Boolean` @@ -699,7 +704,7 @@ Use the HeaderStyle property to control the appearance of GridTableView control in the form Property-Subproperty, where Subproperty is a property of the GridTableItemStyle object (for example, - HeaderStyle-ForeColor).Nest a element between the opening + HeaderStyle-ForeColor).Nest a `` element between the opening and closing tags of the GridTableView control.The properties can also be set programmatically in the form Property.Subproperty (for example, HeaderStyle.ForeColor). Common settings usually include a custom @@ -959,7 +964,7 @@ Use the PagerStyle property to control the appearance of the GridTableView control in the form Property-Subproperty, where Subproperty is a property of the GridPagerStyle object (for example, - PagerStyle-ForeColor).Nest a element between the opening + PagerStyle-ForeColor).Nest a `` element between the opening and closing tags of the GridTableView control.The properties can also be set programmatically in the form Property.Subproperty (for example, PagerStyle.ForeColor). Common settings usually include a custom @@ -1158,7 +1163,7 @@ Use the SelectedItemStyle property to control the appearance GridTableView control in the form Property-Subproperty, where Subproperty is a property of the Style object (for example, - SelectedItemStyle-ForeColor).Nest a element between the + SelectedItemStyle-ForeColor).Nest a `` element between the opening and closing tags of the GridTableView control.The properties can also be set programmatically in the form Property.Subproperty (for example, SelectedItemStyle.ForeColor). Common settings usually include a @@ -1232,7 +1237,7 @@ Gets or sets the tab index of the Web server control. ### TableLayout `GridTableLayout` Gets or sets a string that indicates whether the table layout is fixed. - + #### Remarks The value of the TableLayout property is a string that specifies or receives one of the following GridTableLayout @@ -1910,3 +1915,4 @@ The dictionary which contains all column groups `System.Void` + diff --git a/api/server/Telerik.Web.UI/RadScriptManager.md b/api/server/Telerik.Web.UI/RadScriptManager.md index 7debf374a3..2d0b13f2f7 100644 --- a/api/server/Telerik.Web.UI/RadScriptManager.md +++ b/api/server/Telerik.Web.UI/RadScriptManager.md @@ -34,9 +34,9 @@ Gets the CDN settings. Specifies whether the embedded jQuery library is output with RadControls' scripts. #### Remarks -If the embedded jQuery is disabled, you must manually load a version of jQuery on the page and ensure that - RadControls are compatible with it. If this property is set to false and no compatible jQuery library is used, - the page will throw JavaScript exceptions. +If the embedded jQuery is disabled, you must manually load a version of jQuery on the page and ensure that +RadControls are compatible with it. If this property is set to false and no compatible jQuery library is used, +the page will throw JavaScript exceptions. ### EnableHandlerDetection `Boolean` @@ -45,9 +45,9 @@ Gets or sets a value indicating if RadScriptManager should check the Telerik.Web #### Remarks When EnableHandlerDetection set to true, RadScriptManager automatically checks if the - HttpHandler it uses is registered to the application configuration file and throws - an exception if the HttpHandler registration missing. Set this property to false - if your scenario uses a file to output the combined scripts, or when running in Medium trust. +HttpHandler it uses is registered to the application configuration file and throws +an exception if the HttpHandler registration missing. Set this property to false +if your scenario uses a file to output the combined scripts, or when running in Medium trust. ### EnableScriptCombine `Boolean` @@ -55,10 +55,10 @@ Specifies whether or not multiple script references should be combined into a si #### Remarks When EnableScriptCombine set to true, the script references of the controls - on the page are combined to a single file, so that only one - ```` + + ```` diff --git a/controls/calendar/appearance-and-styling/html-output.md b/controls/calendar/appearance-and-styling/html-output.md index 616062e5ba..48177f5fdb 100644 --- a/controls/calendar/appearance-and-styling/html-output.md +++ b/controls/calendar/appearance-and-styling/html-output.md @@ -1,151 +1,151 @@ ---- -title: HTML Output -page_title: HTML Output - RadCalendar -description: Check our Web Forms article about HTML Output. -slug: calendar/appearance-and-styling/html-output -tags: html,output -published: True -position: 4 ---- - -# HTML Output - - - -Styles for Telerik controls are defined using Cascading Style Sheet (CSS) syntax. Each style consists of a selector that identifies an HTML element to be styled, and property/value pairs that describe each of the style specifics, e.g. color, padding, margins, etc. For example, the **table.RadCalendar_Default** style defines the default width and font styles for the entire calendar control: - -````CSS -table.RadCalendar_Default -{ - border-collapse:separate; - border:0; - font:11px arial,tahoma,sans-serif; - width:220px; -} -```` - - - -See [CSS Skin Selectors]({%slug calendar/appearance-and-styling/css-skin-selectors%}) for detailed information on the specific CSS selectors used for the [ASP NET AJAX Calendar](https://www.telerik.com/products/aspnet-ajax/calendar.aspx) skins. - -## HTML Output of RadCalendar - -The typical HTML output of a **RadCalendar** control is the following (some HTML attributes have been removed for simplicity): - -````HTML -
- - - - - - - - - - - -
- - - - - - - - -
- << - - < - - May 2010 - - > - - >> -
-
- - - - - - - - - - - - - - - - - - ..... - - - ...... - -
- x - - Su - - Mo - - Tu - - We - - Th - - Fr - - Sa -
- 18 - - 25 -
-
- - -
-```` - - - -* **div#ClientID_wrapper** - this element is not used for any styling, it only wraps the control - -* **table.RadCalendar.RadCalendar_*SkinName*** - this is the main control element, which holds the skin name. It has a <*thead*> child element, which contains the header area, and a <*tbody*> child element, which contains the date matrix. - -* **td.rcTitlebar** - the table cell, which wraps all elements in the header area. It contains another <*table*> and every cell of this table contains a specific element from the header (navigation arrows or title label). When month navigation is disabled (**EnableNavigation="false"**), the table cell has one more CSS class - **rcNoNav**. - -* **a.rcFastPrev**, **a.rcPrev**, **a.Next**, **a.rcFastNext** - the navigation buttons in the header area. - -* **td.rcTitle** - the table cell, which contains the control's title - the current month and year in the specified **TitleFormat**. - -* **td.rcMain** - the table cell, which wraps all elements in the date matrix. It contains another and every cell of this table contains either a day number, or a weekday name, or a week number - -* **table.rcMainTable** - the table populated with the date matrix, mentioned in the previous list item. It has a <*thead*> child, which contains the column headers (usually the weekday names) and a <*tbody*> child, which contains the row headers (usually the week numbers) and the date cells - -* **tr.rcWeek** - the column header row, which contains the weekday names, each in a separate <*th*> element. Depends on the **ShowColumnHeaders** property. If you set **Orientation="RenderInColumns"**, it will contain the week numbers - -* **th.rcViewSel** - the table header cell, which acts as a view selector - if the user clicks it, all dates will be (un)selected. Depends on the **EnableViewSelector** property - -* **tr.rcRow** - a date matrix table row, which contains day cells. The day cells can have several different CSS classes, depending on their state - **rcToday**, **rcWeekend**, **rcOtherMonth**, **rcOutOfRange** (used with RadDatePicker only). All states obtain the same CSS classes on hover and select - **rcHover** and **rcSelected** - -* each day cell contains an <*a*> element inside with the day number, while out-of-range day cells contain a <*span*> element. Of course, this does not apply in the case when special day templates are used - - -## Notes on skinning - -* If you intend to use border styles for the **RadCalendar** table cells, then the **border-collapse** CSS style of all <*table*> elements in these controls must be set to **separate**. - -* The width of **RadCalendar** depends on the length of the titlebar content (i.e. the month name). In order to prevent resizing when navigating to another month, the control should have a default width (220px set in the Calendar base stylesheet). - -* The **RadCalendar** navigation buttons and the **RadDateTimePicker** popup buttons have the following styles by default. This way the buttons can use background images of a set size and no visible text (it is shifted to the left) - **display:block; overflow:hidden; text-indent:-2222px; text-decoration:none;** - - +--- +title: HTML Output +page_title: HTML Output - RadCalendar +description: Check our Web Forms article about HTML Output. +slug: calendar/appearance-and-styling/html-output +tags: html,output +published: True +position: 4 +--- + +# HTML Output + + + +Styles for Telerik controls are defined using Cascading Style Sheet (CSS) syntax. Each style consists of a selector that identifies an HTML element to be styled, and property/value pairs that describe each of the style specifics, e.g. color, padding, margins, etc. For example, the **table.RadCalendar_Default** style defines the default width and font styles for the entire calendar control: + +````CSS +table.RadCalendar_Default +{ + border-collapse:separate; + border:0; + font:11px arial,tahoma,sans-serif; + width:220px; +} +```` + + + +See [CSS Skin Selectors]({%slug calendar/appearance-and-styling/css-skin-selectors%}) for detailed information on the specific CSS selectors used for the [ASP NET AJAX Calendar](https://www.telerik.com/products/aspnet-ajax/calendar.aspx) skins. + +## HTML Output of RadCalendar + +The typical HTML output of a **RadCalendar** control is the following (some HTML attributes have been removed for simplicity): + +````HTML +
+
+ + + + + + + + + + +
+ + + + + + + + +
+ << + + < + + May 2010 + + > + + >> +
+
+ + + + + + + + + + + + + + + + + + ..... + + + ...... + +
+ x + + Su + + Mo + + Tu + + We + + Th + + Fr + + Sa +
+ 18 + + 25 +
+
+ + + +```` + + + +* **div#ClientID_wrapper** - this element is not used for any styling, it only wraps the control + +* **table.RadCalendar.RadCalendar_*SkinName*** - this is the main control element, which holds the skin name. It has a <*thead*> child element, which contains the header area, and a <*tbody*> child element, which contains the date matrix. + +* **td.rcTitlebar** - the table cell, which wraps all elements in the header area. It contains another <*table*> and every cell of this table contains a specific element from the header (navigation arrows or title label). When month navigation is disabled (**EnableNavigation="false"**), the table cell has one more CSS class - **rcNoNav**. + +* **a.rcFastPrev**, **a.rcPrev**, **a.Next**, **a.rcFastNext** - the navigation buttons in the header area. + +* **td.rcTitle** - the table cell, which contains the control's title - the current month and year in the specified **TitleFormat**. + +* **td.rcMain** - the table cell, which wraps all elements in the date matrix. It contains another <*table*> and every cell of this table contains either a day number, or a weekday name, or a week number + +* **table.rcMainTable** - the table populated with the date matrix, mentioned in the previous list item. It has a <*thead*> child, which contains the column headers (usually the weekday names) and a <*tbody*> child, which contains the row headers (usually the week numbers) and the date cells + +* **tr.rcWeek** - the column header row, which contains the weekday names, each in a separate <*th*> element. Depends on the **ShowColumnHeaders** property. If you set **Orientation="RenderInColumns"**, it will contain the week numbers + +* **th.rcViewSel** - the table header cell, which acts as a view selector - if the user clicks it, all dates will be (un)selected. Depends on the **EnableViewSelector** property + +* **tr.rcRow** - a date matrix table row, which contains day cells. The day cells can have several different CSS classes, depending on their state - **rcToday**, **rcWeekend**, **rcOtherMonth**, **rcOutOfRange** (used with RadDatePicker only). All states obtain the same CSS classes on hover and select - **rcHover** and **rcSelected** + +* each day cell contains an <*a*> element inside with the day number, while out-of-range day cells contain a <*span*> element. Of course, this does not apply in the case when special day templates are used + + +## Notes on skinning + +* If you intend to use border styles for the **RadCalendar** table cells, then the **border-collapse** CSS style of all <*table*> elements in these controls must be set to **separate**. + +* The width of **RadCalendar** depends on the length of the titlebar content (i.e. the month name). In order to prevent resizing when navigating to another month, the control should have a default width (220px set in the Calendar base stylesheet). + +* The **RadCalendar** navigation buttons and the **RadDateTimePicker** popup buttons have the following styles by default. This way the buttons can use background images of a set size and no visible text (it is shifted to the left) - **display:block; overflow:hidden; text-indent:-2222px; text-decoration:none;** + + diff --git a/controls/calendar/templates/day-templates.md b/controls/calendar/templates/day-templates.md index 0a4f9fef8f..18594d5d6d 100644 --- a/controls/calendar/templates/day-templates.md +++ b/controls/calendar/templates/day-templates.md @@ -36,7 +36,7 @@ The following steps describe how to implement Day Templates: -```` + ```` @@ -73,7 +73,7 @@ The following steps describe how to implement Day Templates: -```` + ```` @@ -118,7 +118,7 @@ The following steps describe how to implement Day Templates: -```` + ```` 2. You can also add special days dynamically at runtime: diff --git a/controls/chart/troubleshooting/telerik.charting-type-in-both-telerik.charting.dll-and-radchart.net2.dll.md b/controls/chart/troubleshooting/telerik.charting-type-in-both-telerik.charting.dll-and-radchart.net2.dll.md index 17da2a4ea5..aed268fe41 100644 --- a/controls/chart/troubleshooting/telerik.charting-type-in-both-telerik.charting.dll-and-radchart.net2.dll.md +++ b/controls/chart/troubleshooting/telerik.charting-type-in-both-telerik.charting.dll-and-radchart.net2.dll.md @@ -8,7 +8,7 @@ published: True position: 1 --- -# Telerik.Charting. in both Telerik.Charting.dll and RadChart.Net2.dll +# Telerik.Charting.<type> in both Telerik.Charting.dll and RadChart.Net2.dll >caution **RadChart** has been replaced by [RadHtmlChart](https://www.telerik.com/products/aspnet-ajax/html-chart.aspx), Telerik's client-side charting component. If you are considering **RadChart** for new development, examine the [RadHtmlChart documentation]({%slug htmlchart/overview%}) and [online demos](https://demos.telerik.com/aspnet-ajax/htmlchart/examples/overview/defaultcs.aspx) first to see if it will fit your development needs. If you are already using **RadChart** in your projects, you can migrate to **RadHtmlChart** by following these articles: [Migrating Series]({%slug htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart/migrate-series-configuration%}), [Migrating Axes]({%slug htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart/migrate-axes-configuration%}), [Migrating Date Axes]({%slug htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart/migrate-date-axis-configuration%}), [Migrating Databinding]({%slug htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart/migrate-data-binding-configuration%}), [Features parity]({%slug htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart/migrate-functionalities---features-and-series-types-parity%}). Support for **RadChart** is discontinued as of **Q3 2014**, but the control will remain in the assembly so it can still be used. We encourage you to use **RadHtmlChart** for new development. diff --git a/controls/combobox/client-side-programming/overview.md b/controls/combobox/client-side-programming/overview.md index 635649f40c..1cae144bb7 100644 --- a/controls/combobox/client-side-programming/overview.md +++ b/controls/combobox/client-side-programming/overview.md @@ -1,197 +1,197 @@ ---- -title: Overview -page_title: Client-side Overview - RadComboBox -description: Check our Web Forms article about Overview. -slug: combobox/client-side-programming/overview -tags: overview -published: True -position: 0 ---- - -# Client-side Programming Overview - - - -**RadComboBox** provides a flexible client-side API. You can easily interact with **RadComboBox** in the browser using its client-side object. In addition to a variety of [client-side events]({%slug combobox/client-side-programming/events%}), the client-side object model lets you achieve complicated tasks while avoiding unnecessary postbacks. - -## Getting the RadComboBox Client-side Object - -**RadComboBox** creates a client-side object with its **ClientID**. You can obtain the reference using the following JavaScript code: - -````JavaScript - -var combo = $find("<%= RadComboBox1.ClientID %>"); - -```` - - - -## Getting the Instance of a Particular RadComboBoxItem - -Once you have a reference to the client-side object of **RadComboBox**, you can use the **findItemByText()** method to get the instance of a particular item: - -````JavaScript - -var combo = $find("<%= RadComboBox1.ClientID %>"); -var item = combo.findItemByText(text); - -```` - - - -## Cancelling an Event - -Several client-side events occur immediately before **RadComboBox** performs an action. Most of these events have names that end with "-ing". You can use these events to cancel the **RadComboBox's** action by using the **set_cancel** method of the **eventArgs** that are passed to the handler: - -````JavaScript - -function OnClientSelectedIndexChanging(sender, eventArgs) { - eventArgs.set_cancel(true); -} - -```` - - - -## Calling a Client-side Method - -When you get the instance of a **RadComboBox** object, you can call client-side methods to perform certain tasks. Consider the following examples: - -* **showDropDown()** - -````JavaScript - -function ShowDropDownFunction() { - var combo = $find("<%= RadComboBox1.ClientID %>"); - combo.showDropDown(); -} - -```` - - - -* **hideDropDown()** - -````JavaScript - -function HideDropDownFunction() { - var combo = $find("<%= RadComboBox1.ClientID %>"); - combo.hideDropDown(); -} - -```` - - - -* **disable()** - -````JavaScript - -function DisableComboBox() { - var combo = $find("<%= RadComboBox1.ClientID %>"); - combo.disable(); -} - -```` - - - -* **enable()** - -````JavaScript - -function EnableComboBox() { - var combo = $find("<%= RadComboBox1.ClientID %>"); - combo.enable(); -} - -```` - - - -* **RadComboBoxItem.select()** - -````JavaScript - -function SelectComboBoxItem(itemText) { - var combo = $find("<%= RadComboBox1.ClientID %>"); - var item = combo.findItemByText(itemText); - if (item) { - item.select(); - } -} - -```` - - - -## Preserving Changes - -By default, changes made in client-side code do not persist over a postback to the server. To preserve changes, you must use the **trackChanges** and **commitChanges** methods, as shown in **Example 1**: - -**Example 1:** Adding an item on the client-side and persisting the change over a postback to the server. - -````JavaScript - -function AddNewItem() { - var combo = $find("<%= RadComboBox1.ClientID %>"); - var comboItem = new Telerik.Web.UI.RadComboBoxItem(); - comboItem.set_text("item"); - combo.trackChanges(); - combo.get_items().add(comboItem); - comboItem.select(); - combo.commitChanges(); -} - -```` - - - ->note This approach does not affect Items loaded on demand. By design, they are [lost after postback]({%slug combobox/troubleshooting/radcombobox-items-are-not-accessible-on-the-server-side-when-loading-them-on-demand%}). -> - - -## Getting All RadComboBox Instances on the Client-side - -**RadComboBox** exposes an array on the client-side that contains all **RadComboBox** instances. You can access this array using syntax like this: **Telerik.Web.UI.RadComboBox.ComboBoxes**. - -If **RadComboBox** controls are embedded in another control, you can simply get these controls from the array using code like **Example 2.** - -**Example 2:** Finding all RadComboBox instances on the page. - -````ASPNET - - - - ... - - - - - - ... - - -```` - -## Next Steps - -[Access client-side changes at the server]({%slug combobox/client-side-programming/accessing-client-changes-at-the-server%}) - -[Explore the RadComboBox client-side events]({%slug combobox/client-side-programming/events%}) - -# See Also - - * [RadComboBox Object]({%slug combobox/client-side-programming/objects/radcombobox-object%}) - - * [RadComboBoxItemCollection Object]({%slug combobox/client-side-programming/objects/radcomboboxitemcollection-object%}) - - * [RadComboBoxItem Object]({%slug combobox/client-side-programming/objects/radcomboboxitem-object%}) - - * [Events]({%slug combobox/client-side-programming/events%}) +--- +title: Overview +page_title: Client-side Overview - RadComboBox +description: Check our Web Forms article about Overview. +slug: combobox/client-side-programming/overview +tags: overview +published: True +position: 0 +--- + +# Client-side Programming Overview + + + +**RadComboBox** provides a flexible client-side API. You can easily interact with **RadComboBox** in the browser using its client-side object. In addition to a variety of [client-side events]({%slug combobox/client-side-programming/events%}), the client-side object model lets you achieve complicated tasks while avoiding unnecessary postbacks. + +## Getting the RadComboBox Client-side Object + +**RadComboBox** creates a client-side object with its **ClientID**. You can obtain the reference using the following JavaScript code: + +````JavaScript + +var combo = $find("<%= RadComboBox1.ClientID %>"); + +```` + + + +## Getting the Instance of a Particular RadComboBoxItem + +Once you have a reference to the client-side object of **RadComboBox**, you can use the **findItemByText()** method to get the instance of a particular item: + +````JavaScript + +var combo = $find("<%= RadComboBox1.ClientID %>"); +var item = combo.findItemByText(text); + +```` + + + +## Cancelling an Event + +Several client-side events occur immediately before **RadComboBox** performs an action. Most of these events have names that end with "-ing". You can use these events to cancel the **RadComboBox's** action by using the **set_cancel** method of the **eventArgs** that are passed to the handler: + +````JavaScript + +function OnClientSelectedIndexChanging(sender, eventArgs) { + eventArgs.set_cancel(true); +} + +```` + + + +## Calling a Client-side Method + +When you get the instance of a **RadComboBox** object, you can call client-side methods to perform certain tasks. Consider the following examples: + +* **showDropDown()** + +````JavaScript + +function ShowDropDownFunction() { + var combo = $find("<%= RadComboBox1.ClientID %>"); + combo.showDropDown(); +} + +```` + + + +* **hideDropDown()** + +````JavaScript + +function HideDropDownFunction() { + var combo = $find("<%= RadComboBox1.ClientID %>"); + combo.hideDropDown(); +} + +```` + + + +* **disable()** + +````JavaScript + +function DisableComboBox() { + var combo = $find("<%= RadComboBox1.ClientID %>"); + combo.disable(); +} + +```` + + + +* **enable()** + +````JavaScript + +function EnableComboBox() { + var combo = $find("<%= RadComboBox1.ClientID %>"); + combo.enable(); +} + +```` + + + +* **RadComboBoxItem.select()** + +````JavaScript + +function SelectComboBoxItem(itemText) { + var combo = $find("<%= RadComboBox1.ClientID %>"); + var item = combo.findItemByText(itemText); + if (item) { + item.select(); + } +} + +```` + + + +## Preserving Changes + +By default, changes made in client-side code do not persist over a postback to the server. To preserve changes, you must use the **trackChanges** and **commitChanges** methods, as shown in **Example 1**: + +**Example 1:** Adding an item on the client-side and persisting the change over a postback to the server. + +````JavaScript + +function AddNewItem() { + var combo = $find("<%= RadComboBox1.ClientID %>"); + var comboItem = new Telerik.Web.UI.RadComboBoxItem(); + comboItem.set_text("item"); + combo.trackChanges(); + combo.get_items().add(comboItem); + comboItem.select(); + combo.commitChanges(); +} + +```` + + + +>note This approach does not affect Items loaded on demand. By design, they are lost after postback). +> + + +## Getting All RadComboBox Instances on the Client-side + +**RadComboBox** exposes an array on the client-side that contains all **RadComboBox** instances. You can access this array using syntax like this: **Telerik.Web.UI.RadComboBox.ComboBoxes**. + +If **RadComboBox** controls are embedded in another control, you can simply get these controls from the array using code like **Example 2.** + +**Example 2:** Finding all RadComboBox instances on the page. + +````ASPNET + + + + ... + + + + + + ... + + +```` + +## Next Steps + +[Access client-side changes at the server]({%slug combobox/client-side-programming/accessing-client-changes-at-the-server%}) + +[Explore the RadComboBox client-side events]({%slug combobox/client-side-programming/events%}) + +# See Also + + * [RadComboBox Object]({%slug combobox/client-side-programming/objects/radcombobox-object%}) + + * [RadComboBoxItemCollection Object]({%slug combobox/client-side-programming/objects/radcomboboxitemcollection-object%}) + + * [RadComboBoxItem Object]({%slug combobox/client-side-programming/objects/radcomboboxitem-object%}) + + * [Events]({%slug combobox/client-side-programming/events%}) diff --git a/controls/editor/how-to/paste-at-cursor-position.md b/controls/editor/how-to/paste-at-cursor-position.md index 5c917c3448..957fed1713 100644 --- a/controls/editor/how-to/paste-at-cursor-position.md +++ b/controls/editor/how-to/paste-at-cursor-position.md @@ -23,7 +23,7 @@ To achieve this, you need to: 1. **Obtain the needed HTML** according to your business logic and UX requirements. You can find some tips on requesting complex content from the server in the [Different ways to make a request to the server in ASP.NET](https://www.telerik.com/blogs/different-ways-to-make-a-request-to-the-server) blog post. -1. **Restore the cursor position** by using the [select() DomRange method](/api/client/Telerik.Web.UI.Editor.DomRange). +1. **Restore the cursor position** by using the [select() DomRange method](slug://Telerik.Web.UI.Editor.DomRange). 1. **Paste programmatically** by using the [pasteHtml() method]({%slug editor/client-side-programming/methods/pastehtml%}). @@ -65,7 +65,7 @@ Type text, select content or move the cursor in the editor and click the button ## See Also -* [RadEditor's DomRange method](/devtools/aspnet-ajax/api/client/Telerik.Web.UI.Editor.DomRange) +* [RadEditor's DomRange method](slug://Telerik.Web.UI.Editor.DomRange) * [OnClientSelectionChange Event]({%slug editor/client-side-programming/events/onclientselectionchange%}) diff --git a/controls/editor/troubleshooting/cannot-deserialize-dialog-parameters.-invalid-character-in-a-base-64-string..md b/controls/editor/troubleshooting/cannot-deserialize-dialog-parameters.-invalid-character-in-a-base-64-string.md similarity index 98% rename from controls/editor/troubleshooting/cannot-deserialize-dialog-parameters.-invalid-character-in-a-base-64-string..md rename to controls/editor/troubleshooting/cannot-deserialize-dialog-parameters.-invalid-character-in-a-base-64-string.md index cabcd5a5e0..b95cb0c48b 100644 --- a/controls/editor/troubleshooting/cannot-deserialize-dialog-parameters.-invalid-character-in-a-base-64-string..md +++ b/controls/editor/troubleshooting/cannot-deserialize-dialog-parameters.-invalid-character-in-a-base-64-string.md @@ -1,37 +1,37 @@ ---- -title: Cannot Deserialize Dialog Parameters. Invalid character in a Base-64 string. -page_title: Cannot Deserialize Dialog Parameters. Invalid character in a Base-64 string. - RadEditor -description: Check our Web Forms article about Cannot Deserialize Dialog Parameters. Invalid character in a Base-64 string. -slug: editor/troubleshooting/cannot-deserialize-dialog-parameters.-invalid-character-in-a-base-64-string. -tags: cannot,deserialize,dialog,parameters.,invalid,character,in,a,base-64,string. -published: True -position: 5 ---- - -# Cannot Deserialize Dialog Parameters. Invalid character in a Base-64 string. - -**Error:** - -Cannot Deserialize Dialog Parameters. Invalid character in a Base-64 string. - -![](images/editor-radspellerror.jpg) - -**Solution:** - -The way dialog parameters are serialized was changed due to a security issue in a previous release of the Telerik® UI for ASP.NET AJAX. The parameters are now using a random key each time the application is restarted. This means that if the user leaves the page in the browser and the application is restarted, the spell dialog will stop working after that, because the encryption key has changed. - -A specific encryption key could be forced for the editor/spell dialogs with the following application setting in the web.config: - -You can use any combination of letters and numbers - the key has no specific format. 46 bytes is 46 characters. - -````XML - - - -```` - - - -This way the dialogs will always use the same key and the "cannot deserialize..." error will not appear even after the application is restarted. - -The same workaround is used if the web application is hosted in a web farm scenario where multiple web servers are used to handle page requests. +--- +title: Cannot Deserialize Dialog Parameters. Invalid character in a Base-64 string. +page_title: Cannot Deserialize Dialog Parameters. Invalid character in a Base-64 string. - RadEditor +description: Check our Web Forms article about Cannot Deserialize Dialog Parameters. Invalid character in a Base-64 string. +slug: editor/troubleshooting/cannot-deserialize-dialog-parameters.-invalid-character-in-a-base-64-string. +tags: cannot,deserialize,dialog,parameters.,invalid,character,in,a,base-64,string. +published: True +position: 5 +--- + +# Cannot Deserialize Dialog Parameters. Invalid character in a Base-64 string. + +**Error:** + +Cannot Deserialize Dialog Parameters. Invalid character in a Base-64 string. + +![](images/editor-radspellerror.jpg) + +**Solution:** + +The way dialog parameters are serialized was changed due to a security issue in a previous release of the Telerik® UI for ASP.NET AJAX. The parameters are now using a random key each time the application is restarted. This means that if the user leaves the page in the browser and the application is restarted, the spell dialog will stop working after that, because the encryption key has changed. + +A specific encryption key could be forced for the editor/spell dialogs with the following application setting in the web.config: + +You can use any combination of letters and numbers - the key has no specific format. 46 bytes is 46 characters. + +````XML + + + +```` + + + +This way the dialogs will always use the same key and the "cannot deserialize..." error will not appear even after the application is restarted. + +The same workaround is used if the web application is hosted in a web farm scenario where multiple web servers are used to handle page requests. diff --git a/controls/formdecorator/appearance-and-styling/primary-action-button.md b/controls/formdecorator/appearance-and-styling/primary-action-button.md index 739d774414..a35cb08b70 100644 --- a/controls/formdecorator/appearance-and-styling/primary-action-button.md +++ b/controls/formdecorator/appearance-and-styling/primary-action-button.md @@ -24,9 +24,6 @@ To switch to a primary action button, add the `rfdPrimaryButton` class to the de ```` -@[template](/_templates/common/primary-action-button.md#intro-test "val1: A button decorated by **RadFormDecorator**, val2: decorated button") - - ## See Also * [Create a Custom Skin]({%slug formdecorator/appearance-and-styling/tutorial-creating-custom-lightweight-skin%}) diff --git a/controls/grid/accessing-values-and-controls/server-side/accessing-cells.md b/controls/grid/accessing-values-and-controls/server-side/accessing-cells.md index 31b1075005..c1230c692c 100644 --- a/controls/grid/accessing-values-and-controls/server-side/accessing-cells.md +++ b/controls/grid/accessing-values-and-controls/server-side/accessing-cells.md @@ -115,7 +115,7 @@ Protected Sub RadGrid1_ItemCommand(sender As Object, e As GridCommandEventArgs) End Sub ```` ->tip If you are using detail tables, you may want to check the `item.OwnerTableView.Name` you are accessing to prevent null reference errors. You can find [here](access-parent-data.zip) an example that explains in detail how this is done and how to get data from parent tables as well. +>tip If you are using detail tables, you may want to check the `item.OwnerTableView.Name` you are accessing to prevent null reference errors. ## Accessing Cells in DataItem diff --git a/controls/grid/appearance-and-styling/set-style-on-mouse-over.md b/controls/grid/appearance-and-styling/set-style-on-mouse-over.md index 6efc77e60e..e035fccd22 100644 --- a/controls/grid/appearance-and-styling/set-style-on-mouse-over.md +++ b/controls/grid/appearance-and-styling/set-style-on-mouse-over.md @@ -1,101 +1,99 @@ ---- -title: Set style on mouse over -page_title: Set style on mouse over - RadGrid -description: Check our Web Forms article about Set style on mouse over. -slug: grid/appearance-and-styling/set-style-on-mouse-over -tags: set,style,on,mouse,over -published: True -position: 6 ---- - -# Set style on mouse over - -Sometimes, it may be necessary to style a given row/header in Telerik RadGrid, whenever the user hovers with the mouse over it. With RadGrid this functionality is easily achievable. The control provides a CSS class like *GridRowOver_*. Such style is present under each embedded skin and defines the visual appearance of the hovered grid row. For example: - -````CSS -.GridRowOver_[SkinName] -{ -background-color: orange; -cursor:pointer; -} -```` - - - -To enable the hover style for the grid rows, merely set the **ClientSettings -> EnableRowHoverStyle** property of RadGrid to true. - ->note This depends on RadGrid client-side object. For performance reasons, the RadGrid client object is available only when certain client features/events are enabled. If no client features/events are available in the grid but you still need this functionality, you can attach an empty javascript function to a client event (for example OnRowClick). -> - - -If you want to attain the same functionality without the built-in feature of RadGrid for ASP.NET AJAX or with disabled skins, the steps below show how to achieve this: - -1. Create the Telerik RadGrid instance and the data source to which it will be bound. - -2. Create a style class, in the head section of the .aspx code, which will be used to style the active row/header. This may look something like this: - - **CSS** - - - - -3. This particular approach relies on the **OnRowMouseOver**, **OnRowMouseOut**, **OnColumnMouseOver** and **OnColumnMouseOut** client-side functions, to use the style mentioned above. Declare these functions in the **ClientSettings ->ClientEvents** section of the grid declaration like this: - - **ASP.NET** - - - - - - -4. Before the grid tag on the page or in the head section, include the client-side JavaScript functions mentioned above: - - **JavaScript** - - - - -After these steps have been performed, when the user hovers with the mouse over the control, the styles mentioned above will be applied, as shown in the following screenshot: - -![Set Row Style On Hover](images/grd_SerRowStyleOnHover.png) - -## See Also - - * [Customizing Row Appearance]({%slug grid/appearance-and-styling/customizing-row-appearance%}) - - * [Adding Tooltips for Grid Items]({%slug grid/appearance-and-styling/adding-tooltips-for-grid-items%}) - - * [Conditional Formatting]({%slug grid/appearance-and-styling/conditional-formatting%}) +--- +title: Set style on mouse over +page_title: Set style on mouse over - RadGrid +description: Check our Web Forms article about Set style on mouse over. +slug: grid/appearance-and-styling/set-style-on-mouse-over +tags: set,style,on,mouse,over +published: True +position: 6 +--- + +# Set style on mouse over + +Sometimes, it may be necessary to style a given row/header in Telerik RadGrid, whenever the user hovers with the mouse over it. With RadGrid this functionality is easily achievable. The control provides a CSS class like *GridRowOver_<SkinName>*. Such style is present under each embedded skin and defines the visual appearance of the hovered grid row. For example: + +````CSS +.GridRowOver_[SkinName] +{ +background-color: orange; +cursor:pointer; +} +```` + + + +To enable the hover style for the grid rows, merely set the **ClientSettings -> EnableRowHoverStyle** property of RadGrid to true. + +>note This depends on RadGrid client-side object. For performance reasons, the RadGrid client object is available only when certain client features/events are enabled. If no client features/events are available in the grid but you still need this functionality, you can attach an empty javascript function to a client event (for example OnRowClick). +> + + +If you want to attain the same functionality without the built-in feature of RadGrid for ASP.NET AJAX or with disabled skins, the steps below show how to achieve this: + +1. Create the Telerik RadGrid instance and the data source to which it will be bound. + +2. Create a style class, in the head section of the .aspx code, which will be used to style the active row/header. This may look something like this: + + ````CSS + + ```` + + +3. This particular approach relies on the **OnRowMouseOver**, **OnRowMouseOut**, **OnColumnMouseOver** and **OnColumnMouseOut** client-side functions, to use the style mentioned above. Declare these functions in the **ClientSettings ->ClientEvents** section of the grid declaration like this: + + ````ASP.NET + + + + ```` + +4. Before the grid tag on the page or in the head section, include the client-side JavaScript functions mentioned above: + + ````Javascript + + ```` + +After these steps have been performed, when the user hovers with the mouse over the control, the styles mentioned above will be applied, as shown in the following screenshot: + +![Set Row Style On Hover](images/grd_SerRowStyleOnHover.png) + +## See Also + + * [Customizing Row Appearance]({%slug grid/appearance-and-styling/customizing-row-appearance%}) + + * [Adding Tooltips for Grid Items]({%slug grid/appearance-and-styling/adding-tooltips-for-grid-items%}) + + * [Conditional Formatting]({%slug grid/appearance-and-styling/conditional-formatting%}) diff --git a/controls/grid/data-binding/server-side-binding/programmatic-databinding-using-needdatasource-event.md b/controls/grid/data-binding/server-side-binding/programmatic-databinding-using-needdatasource-event.md index 537ab4cee4..65cdac0ced 100644 --- a/controls/grid/data-binding/server-side-binding/programmatic-databinding-using-needdatasource-event.md +++ b/controls/grid/data-binding/server-side-binding/programmatic-databinding-using-needdatasource-event.md @@ -6,7 +6,7 @@ slug: grid/data-binding/server-side-binding/programmatic-databinding-using-needd tags: programmatic,data-binding,needdatasource,events published: True position: 1 -previous_url: controls/grid/data-binding/understanding-data-binding/server-side-binding/advanced-data-binding-\(using-needdatasource-event\),controls/grid/data-binding/understanding-data-binding/server-side-binding/programmatic-databinding-using-needdatasource-event +previous_url: controls/grid/data-binding/understanding-data-binding/server-side-binding/advanced-data-binding-(using-needdatasource-event),controls/grid/data-binding/understanding-data-binding/server-side-binding/programmatic-databinding-using-needdatasource-event --- # Programmatic Data Binding Using the NeedDataSource Event diff --git a/controls/grid/hierarchical-grid-types-and-load-modes/binding-hierarchical-grids.md b/controls/grid/hierarchical-grid-types-and-load-modes/binding-hierarchical-grids.md index 2b26f21312..a3a2d2e6e2 100644 --- a/controls/grid/hierarchical-grid-types-and-load-modes/binding-hierarchical-grids.md +++ b/controls/grid/hierarchical-grid-types-and-load-modes/binding-hierarchical-grids.md @@ -187,7 +187,7 @@ DetailTable0 (copy 0) -Each copy of the detail tables should be bound in order to have its item populated. **RadGrid** delegates the full control of how this should be done to the developer, i.e. you should only filter or select the records that correspond to each detail table. The only restriction is when this should happen. This is the **DetailTableDataBind** event. **RadGrid** fires this event for each **DetailTable** that is about to be bound. Firing of this event also depends on the [[!] HierarchyLoadMode](hierarchy-load-modes.html) of the corresponding **GridTableView** as stated when it is declared in Step 1. +Each copy of the detail tables should be bound in order to have its item populated. **RadGrid** delegates the full control of how this should be done to the developer, i.e. you should only filter or select the records that correspond to each detail table. The only restriction is when this should happen. This is the **DetailTableDataBind** event. **RadGrid** fires this event for each **DetailTable** that is about to be bound. Firing of this event also depends on the [[!] HierarchyLoadMode](slug://grid/hierarchical-grid-types-and-load-modes/hierarchy-load-modes) of the corresponding **GridTableView** as stated when it is declared in Step 1. * If the **HierarchyLoadMode** is set to **ServerBind**, then the **DetailTableDataBind** event will be fired immediately after the corresponding parent item is bound. diff --git a/controls/grid/how-to/hierarchy/single-expand-in-hierarchical-grid.md b/controls/grid/how-to/hierarchy/single-expand-in-hierarchical-grid.md index d8938491bd..376785e85e 100644 --- a/controls/grid/how-to/hierarchy/single-expand-in-hierarchical-grid.md +++ b/controls/grid/how-to/hierarchy/single-expand-in-hierarchical-grid.md @@ -2,9 +2,8 @@ title: Single Expand in hierarchical grid page_title: Single expand in hierarchical grid - RadGrid description: Check our Web Forms article about Single expand in hierarchical grid. -slug: grid/how-to/hierarchy/single-expand-in-hierarchical-grid +slug: grid/how-to/hierarchy/single-expand-in-hierarchical-grid, grid/hierarchical-grid-types-and-load-modes/how-to/ previous_url: controls/grid/hierarchical-grid-types-and-load-modes/how-to/single-expand-in-hierarchical-grid -slug: grid/hierarchical-grid-types-and-load-modes/how-to/ tags: single,expand,in,hierarchical,grid published: True position: 2 diff --git a/controls/lightbox/getting-started.md b/controls/lightbox/getting-started.md index 396b5fc650..feb1e3f476 100644 --- a/controls/lightbox/getting-started.md +++ b/controls/lightbox/getting-started.md @@ -4,7 +4,7 @@ page_title: Getting Started description: Check our Web Forms article about Getting Started. slug: lightbox/getting-started tags: getting,started -published: Truecontrols +published: True position: 2 --- diff --git a/controls/sitemap/overview.md b/controls/sitemap/overview.md index a35485c22f..c7a468dbc6 100644 --- a/controls/sitemap/overview.md +++ b/controls/sitemap/overview.md @@ -1,63 +1,63 @@ ---- -title: Overview -page_title: RadSiteMap Overview -description: Check our Web Forms article about Overview. -slug: sitemap/overview -tags: overview -published: True -position: 0 -CTAControlName: Sitemap ---- - -# WebForms Sitemap Overview - - - -## - -![WebForms RadSiteMap Templates](images/sitemap_templates.png "WebForms RadSiteMap Templates") - -Improve you web page load time with the flexible, lightweight **RadSiteMap** control for ASP.NET AJAX. This UI component with its efficient semantic rendering gives you a lightning fast solution and highly optimized HTML output. With the ease of Telerik’s SiteMap for ASP.NET AJAX you can organize and list the pages on your web site, customize the layout, choose from a variety of appearance options and templates. Add value to your web site by optimizing it for crawler and search engines with no extra development effort. - -{% if site.has_cta_panels == true %} -{% include cta-panel-overview.html %} -{% endif %} - -**Semantic Rendering for Minimal HTML** - -The Telerik ASP.NET SiteMap implements a highly efficient semantic rendering, which results in minimum HTML output and dramatically improves performance. - -**Flexible layouts** - -You can configure the layout of RadSiteMap in a variety of modes. The nodes can be viewed in either list or flow state. By selecting the flow property items in the group will be arranged in rows one after the other, instead of displaying them as a list. End-users can also alternate between single, multi-column, horizontal or vertical view. In addition you can display node lines in a fashion similar to RadTreeView and collapse the hierarchy. - -**Templates** - -The ASP.NET SiteMap by Telerik allows you to define a collection of dynamic templates that customize the presentation of the hierarchy and the individual nodes. You can apply per-level, per-node and global templates and add extra information, such as images, links to additional sources, etc. - -![WebForms RadSiteMap Overview](images/sitemap_overview.png "WebFormsRadSiteMap Overview") - -**Appearance** - -RadSiteMap is shipped with a rich set of skins that allow you to easily build slick interfaces with the look-and-feel of Windows Vista, Office 2007, Outlook, etc. The skins can be easily switched using a single property. This significantly simplifies styling even for complex configurations. - -**Industry-Best Cross-Browser Support** - -Following our long tradition of industry best cross-browser support, Telerik ASP.NET SiteMap doesn’t make an exception. The component supports all major browsers, including Internet Explorer, Firefox, Safari, Opera and Google Chrome and produces identical results. - -**Search Engine Friendly** - -RadSiteMap completely follows the principles of Search Engine Optimization. The control's innovative rendering generates semantic lists and standard tags, which are properly recognized and highly valued by search engines. As a result, all content accessible through this control will be automatically indexed and ranked with no extra effort required from the developer. - -**Codeless Test Automation for RadSiteMap** - -Now you can record, execute and debug functional tests for RadSiteMap without leaving the familiar Visual Studio environment. Telerik WebUI Test Studio is an advanced click and play web application testing tool specialized for automating ASP.NET AJAX applications. The Studio ships with special translators for Telerik RadControls for ASP.NET AJAX. - -![RadSiteMap List](images/sitemap_list.jpg "RadSiteMap List") - -## See Also - - * [Online Demos](https://demos.telerik.com/aspnet-ajax/sitemap/examples/overview/defaultcs.aspx) - - * [ASP.NET AJAX SiteMap](https://www.telerik.com/products/aspnet-ajax/sitemap.aspx) - +--- +title: Overview +page_title: RadSiteMap Overview +description: Check our Web Forms article about Overview. +slug: sitemap/overview +tags: overview +published: True +position: 0 +CTAControlName: Sitemap +--- + +# WebForms Sitemap Overview + + + +## + +![WebForms RadSiteMap Templates](images/sitemap_templates.png "WebForms RadSiteMap Templates") + +Improve you web page load time with the flexible, lightweight **RadSiteMap** control for ASP.NET AJAX. This UI component with its efficient semantic rendering gives you a lightning fast solution and highly optimized HTML output. With the ease of Telerik’s SiteMap for ASP.NET AJAX you can organize and list the pages on your web site, customize the layout, choose from a variety of appearance options and templates. Add value to your web site by optimizing it for crawler and search engines with no extra development effort. + +{% if site.has_cta_panels == true %} +{% include cta-panel-overview.html %} +{% endif %} + +**Semantic Rendering for Minimal HTML** + +The Telerik ASP.NET SiteMap implements a highly efficient semantic rendering, which results in minimum HTML output and dramatically improves performance. + +**Flexible layouts** + +You can configure the layout of RadSiteMap in a variety of modes. The nodes can be viewed in either list or flow state. By selecting the flow property items in the group will be arranged in rows one after the other, instead of displaying them as a list. End-users can also alternate between single, multi-column, horizontal or vertical view. In addition you can display node lines in a fashion similar to RadTreeView and collapse the hierarchy. + +**Templates** + +The ASP.NET SiteMap by Telerik allows you to define a collection of dynamic templates that customize the presentation of the hierarchy and the individual nodes. You can apply per-level, per-node and global templates and add extra information, such as images, links to additional sources, etc. + +![WebForms RadSiteMap Overview](images/sitemap_overview.png "WebFormsRadSiteMap Overview") + +**Appearance** + +RadSiteMap is shipped with a rich set of skins that allow you to easily build slick interfaces with the look-and-feel of Windows Vista, Office 2007, Outlook, etc. The skins can be easily switched using a single property. This significantly simplifies styling even for complex configurations. + +**Industry-Best Cross-Browser Support** + +Following our long tradition of industry best cross-browser support, Telerik ASP.NET SiteMap doesn’t make an exception. The component supports all major browsers, including Internet Explorer, Firefox, Safari, Opera and Google Chrome and produces identical results. + +**Search Engine Friendly** + +RadSiteMap completely follows the principles of Search Engine Optimization. The control's innovative rendering generates semantic lists and standard `` tags, which are properly recognized and highly valued by search engines. As a result, all content accessible through this control will be automatically indexed and ranked with no extra effort required from the developer. + +**Codeless Test Automation for RadSiteMap** + +Now you can record, execute and debug functional tests for RadSiteMap without leaving the familiar Visual Studio environment. Telerik WebUI Test Studio is an advanced click and play web application testing tool specialized for automating ASP.NET AJAX applications. The Studio ships with special translators for Telerik RadControls for ASP.NET AJAX. + +![RadSiteMap List](images/sitemap_list.jpg "RadSiteMap List") + +## See Also + + * [Online Demos](https://demos.telerik.com/aspnet-ajax/sitemap/examples/overview/defaultcs.aspx) + + * [ASP.NET AJAX SiteMap](https://www.telerik.com/products/aspnet-ajax/sitemap.aspx) + diff --git a/controls/splitbutton/client-side-programming/events/overview.md b/controls/splitbutton/client-side-programming/events/overview.md index 4446d4fd54..b7e861ecc8 100644 --- a/controls/splitbutton/client-side-programming/events/overview.md +++ b/controls/splitbutton/client-side-programming/events/overview.md @@ -24,7 +24,7 @@ The RadSplitButton exposes several client-side events which allow easy and flexi * **[OnClientContextMenuItemClicked (contextMenuItemClicked)]({%slug splitbutton/client-side-programming/events/onclientcontextmenuitemclicked%})** - raised when an Item from the drop down is clicked. -The ContextMenu embedded in RadSplitButton is fully functional control with its own events that can also be used along with the ones of the SplitButton - [Client-side events]({%slug menu/context-menus/radcontextmenu-object%}}#client-side-events) +The ContextMenu embedded in RadSplitButton is fully functional control with its own events that can also be used along with the ones of the SplitButton - [Client-side events]({%slug menu/context-menus/radcontextmenu-object%}#client-side-events) To handle the desired event, the user must set the respective property to the name of the JavaScript function handling the event or to anonymous JavaScript function. Here is an example: diff --git a/controls/splitbutton/mobile-support/render-modes.md b/controls/splitbutton/mobile-support/render-modes.md index 1354455645..b7953025dd 100644 --- a/controls/splitbutton/mobile-support/render-modes.md +++ b/controls/splitbutton/mobile-support/render-modes.md @@ -23,25 +23,25 @@ There are two ways to configure the rendering mode of the controls: * The **RenderMode property** in the markup or in the code-behind that can be used for a particular instance: ````ASPX - - - ```` + + + ```` ````C# - RadSplitButton.RenderMode = Telerik.Web.UI.RenderMode.Lightweight; - ```` -````VB - RadSplitButton.RenderMode = Telerik.Web.UI.RenderMode.Lightweight - ```` + RadSplitButton.RenderMode = Telerik.Web.UI.RenderMode.Lightweight; + ```` + ````VB + RadSplitButton.RenderMode = Telerik.Web.UI.RenderMode.Lightweight + ```` * A **global setting in the web.config** file that will affect the entire application, unless a concrete value is specified for a given control instance: - ````web.config - - - -```` + ````web.config + + + + ```` ## See Also diff --git a/controls/stylesheetmanager/overview.md b/controls/stylesheetmanager/overview.md index 9f24b3e075..d532f7ab2a 100644 --- a/controls/stylesheetmanager/overview.md +++ b/controls/stylesheetmanager/overview.md @@ -44,11 +44,11 @@ RadStyleSheetManager also needs the HttpHandler to be registered in the applicat ````XML - - - - - + + + + + ```` @@ -66,117 +66,117 @@ If the stylesheet combination is not needed for some reason (e.g. debugging) it 1. Adding an assembly as a WebResource: - 1. Add a new project of type **Class Library** to the solution and call it **TelerikCustomSkins**; - - 1. Add a StyleSheet file to the **TelerikCustomSkins** project and call it **TelerikSkinForComboBox**; - - 1. Set it to be an EmbeddedResource (using the Visual Studio Properties pane). **Right-click** the css file -> **Properties** ->choose **Embedded Resource** for **Build Action**; - - 1. Rename **Class1.cs** to **TelerikSkin.cs** in the TelerikCustomSkins project (this is a cosmetic step to create more meaningful names for the files used in this guide); - - 1. Declare **TelerikSkinForComboBox.css** as a WebResource by adding the **WebResource** assembly attribute to the TelerikSkin.cs code file: - - - - ````C# - using System; - using System.Collections.Generic; - using System.Linq; - using System.Text; - using System.Web.UI; - - [assembly: WebResource("TelerikCustomSkins.TelerikSkinForComboBox.css", "text/css")] - namespace TelerikCustomSkins - { - public class TelerikSkin - { - } - } - - ```` - ````VB.NET - Imports System - Imports System.Collections.Generic - Imports System.Linq - Imports System.Text - Imports System.Web.UI - - - Namespace TelerikCustomSkins - Public Class TelerikSkin - End Class - End Namespace - - ```` - - - 1. Copy the content of [My Telerik.Web.UI installation]\Skins\Telerik -> **ComboBox.Telerik.css** to the **TelerikSkinForComboBox.css** file. - - 1. If the skin css file uses images, which you want to store as WebResources, you need to: - - 1. Copy the images to **TelerikCustomSkins** project. For the RadComboBox Telerik skin, the images are located at [My Telerik.Web.UI installation]\Skins\Telerik\ComboBox. Let's create a **ComboBox_Images** folder to store the images. - - 1. Set the images as EmbeddedResources (using the Visual Studio Properties pane); - - 1. Declare an assembly WebResource attribute for each image by adding the WebResource assembly attribute to the TelerikSkin.cs code file: - - - - ````C# - using System.Web.UI; - [assembly: WebResource("TelerikCustomSkins.TelerikSkinForComboBox.css", "text/css")] - [assembly: WebResource("TelerikCustomSkins.ComboBox_Images.rcbArrowCell.gif", "image/gif")] - [assembly: WebResource("TelerikCustomSkins.ComboBox_Images.rcbBg.gif", "image/gif")] - [assembly: WebResource("TelerikCustomSkins.ComboBox_Images.rcbDropDownBg.gif", "image/gif")] - [assembly: WebResource("TelerikCustomSkins.ComboBox_Images.rcbMoreResults.gif", "image/gif")] - [assembly: WebResource("TelerikCustomSkins.ComboBox_Images.Telerik.gif", "image/gif")] - - namespace TelerikCustomSkins - { - public class TelerikSkin - { - } - } - - ```` - ````VB.NET - Imports System.Web.UI - - - - - - - - Namespace TelerikCustomSkins - Public Class TelerikSkin - End Class - End Namespace - - ```` - - - >note Note that ComboBox_Images is the folder which contains the skin images. - > - - - >caution In **Visual Basic** the name of the folder is [not honored](https://msdn.microsoft.com/en-us/library/aa289232(VS.71).aspx) so you need to be careful with the embedded resource name - > - - - 1. Modify the CSS class declaration’s url attribute to contain the web resource path, e.g..imageBg - - ````CSS - - .RadComboBox_Telerik .rcbArrowCell - { - border: 0; - padding: 0; - width: 23px; - background: transparent url('<%=WebResource("TelerikCustomSkins.ComboBox_Images.rcbArrowCell.gif")%>') no-repeat; - } - - ```` + 1. Add a new project of type **Class Library** to the solution and call it **TelerikCustomSkins**; + + 1. Add a StyleSheet file to the **TelerikCustomSkins** project and call it **TelerikSkinForComboBox**; + + 1. Set it to be an EmbeddedResource (using the Visual Studio Properties pane). **Right-click** the css file -> **Properties** ->choose **Embedded Resource** for **Build Action**; + + 1. Rename **Class1.cs** to **TelerikSkin.cs** in the TelerikCustomSkins project (this is a cosmetic step to create more meaningful names for the files used in this guide); + + 1. Declare **TelerikSkinForComboBox.css** as a WebResource by adding the **WebResource** assembly attribute to the TelerikSkin.cs code file: + + + + ````C# + using System; + using System.Collections.Generic; + using System.Linq; + using System.Text; + using System.Web.UI; + + [assembly: WebResource("TelerikCustomSkins.TelerikSkinForComboBox.css", "text/css")] + namespace TelerikCustomSkins + { + public class TelerikSkin + { + } + } + + ```` + ````VB.NET + Imports System + Imports System.Collections.Generic + Imports System.Linq + Imports System.Text + Imports System.Web.UI + + + Namespace TelerikCustomSkins + Public Class TelerikSkin + End Class + End Namespace + + ```` + + + 1. Copy the content of [My Telerik.Web.UI installation]\Skins\Telerik -> **ComboBox.Telerik.css** to the **TelerikSkinForComboBox.css** file. + + 1. If the skin css file uses images, which you want to store as WebResources, you need to: + + 1. Copy the images to **TelerikCustomSkins** project. For the RadComboBox Telerik skin, the images are located at [My Telerik.Web.UI installation]\Skins\Telerik\ComboBox. Let's create a **ComboBox_Images** folder to store the images. + + 1. Set the images as EmbeddedResources (using the Visual Studio Properties pane); + + 1. Declare an assembly WebResource attribute for each image by adding the WebResource assembly attribute to the TelerikSkin.cs code file: + + + + ````C# + using System.Web.UI; + [assembly: WebResource("TelerikCustomSkins.TelerikSkinForComboBox.css", "text/css")] + [assembly: WebResource("TelerikCustomSkins.ComboBox_Images.rcbArrowCell.gif", "image/gif")] + [assembly: WebResource("TelerikCustomSkins.ComboBox_Images.rcbBg.gif", "image/gif")] + [assembly: WebResource("TelerikCustomSkins.ComboBox_Images.rcbDropDownBg.gif", "image/gif")] + [assembly: WebResource("TelerikCustomSkins.ComboBox_Images.rcbMoreResults.gif", "image/gif")] + [assembly: WebResource("TelerikCustomSkins.ComboBox_Images.Telerik.gif", "image/gif")] + + namespace TelerikCustomSkins + { + public class TelerikSkin + { + } + } + + ```` + ````VB.NET + Imports System.Web.UI + + + + + + + + Namespace TelerikCustomSkins + Public Class TelerikSkin + End Class + End Namespace + + ```` + + + >note Note that ComboBox_Images is the folder which contains the skin images. + > + + + >caution In **Visual Basic** the name of the folder is [not honored](https://msdn.microsoft.com/en-us/library/aa289232(VS.71).aspx) so you need to be careful with the embedded resource name + > + + + 1. Modify the CSS class declaration’s url attribute to contain the web resource path, e.g..imageBg + + ````CSS + + .RadComboBox_Telerik .rcbArrowCell + { + border: 0; + padding: 0; + width: 23px; + background: transparent url('<%=WebResource("TelerikCustomSkins.ComboBox_Images.rcbArrowCell.gif")%>') no-repeat; + } + + ```` @@ -186,21 +186,21 @@ If the stylesheet combination is not needed for some reason (e.g. debugging) it 1. Add a StyleSheetReference to the StyleSheets property of RadStyleSheetManager, providing the full StyleSheet resource name and the Assembly it is located in, e.g - ````ASPNET - - - - - - ```` + ````ASPNET + + + + + + ```` * Test the page by adding RadComboBox with Skin="Telerik" and **EnableEmbeddedSkins="False"**. The expected result is that the Telerik skin is successfully applied to RadCombobBox. - ````ASPNET - - ```` + ````ASPNET + + ```` diff --git a/controls/tabstrip/how-to/change-tabs-on-mouseover.md b/controls/tabstrip/how-to/change-tabs-on-mouseover.md index 2d548c3f45..c885ca983a 100644 --- a/controls/tabstrip/how-to/change-tabs-on-mouseover.md +++ b/controls/tabstrip/how-to/change-tabs-on-mouseover.md @@ -11,8 +11,8 @@ position: 0 # Change Tabs on Mouseover - -## Change tabs on mouseover (www.windows.com-like navigation) + +## Change tabs on mouseover (windows.com-like navigation) ````ASPNET
diff --git a/controls/textbox/accessibility-and-internationalization/mouse-wheel-support.md b/controls/textbox/accessibility-and-internationalization/mouse-wheel-support.md index af70ad502c..03fa961c86 100644 --- a/controls/textbox/accessibility-and-internationalization/mouse-wheel-support.md +++ b/controls/textbox/accessibility-and-internationalization/mouse-wheel-support.md @@ -22,7 +22,7 @@ Users can interact with the **RadInput** controls using the mouse wheel. The fol | RadInput Control | Result of using the Mouse Wheel | | ------ | ------ | | **RadTextBox** |If **TextMode** is **MultiLine** and the **Text** is longer than can be displayed by the number of rows that the **Rows** property dictates, scrolling the mouse wheel causes the text in the control to scroll.| -| + # See Also * [Keyboard Support]({%slug radtextbox/accessibility-and-internationalization/keyboard-support%}) diff --git a/controls/toolbar/appearance-and-styling/understanding-the-skin-css-file.md b/controls/toolbar/appearance-and-styling/understanding-the-skin-css-file.md index c4ed1442cf..8a5a4e3940 100644 --- a/controls/toolbar/appearance-and-styling/understanding-the-skin-css-file.md +++ b/controls/toolbar/appearance-and-styling/understanding-the-skin-css-file.md @@ -1,183 +1,183 @@ ---- -title: Understanding the Skin CSS File -page_title: Understanding the Skin CSS File - RadToolBar -description: Check our Web Forms article about Understanding the Skin CSS File. -slug: toolbar/appearance-and-styling/understanding-the-skin-css-file -tags: understanding,the,skin,css,file -published: True -position: 6 ---- - -# Understanding the Skin CSS File - - - -Styles for RadControls are defined using Cascading Style Sheet (CSS) syntax. Each style consists of a selector that identifies an HTML element to be styled, and property/value pairs that describe each of the style specifics, e.g. color, padding, margins, etc. For example, the ".RadToolBar_Green_Horizontal" style shown below sets the background color of the toolbar: - -````ASPNET -.RadToolBar_Green_Horizontal{ background: #90cc90;} -```` - - -See the [CSS Skin FileSelectors]({%slug toolbar/appearance-and-styling/css-skin-file-selectors%}) topic for more information on the specific CSS selectors used for **RadToolBar** skins. - -Each style maps to a "class" attribute in an HTML tag. For example, consider the excerpt from the HTML rendering of a toolbar shown below: - -````HTML -
- -
-```` - - -The control is rendered as a DIV element with the classes "**RadToolBar RadToolBar_Horizontal RadToolBar_Green RadToolBar_Green_Horizontal**". The **RadToolBar** and **RadToolBar_Horizontal** classes are always applied. They define the basic presentation of the toolbar which is common for all skins. The **RadToolBar_Green** and **RadToolBar_Green_Horizontal** classes are applied because the **Skin** property of the toolbar is set to "Green". - ->note If you set the **Style** or **CssClass** property of the toolbar, those settings are applied to this outer DIV element as well. -> - - -## Tool Bar element - -Immediately inside the outer DIV tag for the toolbar (shown above), the rendered toolbar has three more nested DIV elements: - -````HTML -
-
-
- -
-
-
-```` - -These classes are available for skins to achieve intricate effects in the shape of the toolbar. Most skin CSS files use these classes to apply background images to create the rounded edges of the toolbar. - -Inside the three nested DIV tags, the toolbar uses an unordered list (LI) tag to manage the layout of the buttons in the toolbar: - -````HTML - -```` - -This UL tag always has the **.rtbUL** class applied. - -## Tool Bar Items - -Each item in the toolbar is an LI element inside the UL tag: - -````HTML -
  • - -
    • -
  • - -
    • -
  • - -
    • -```` - -The LI element always has the **.rtbItem** class applied.In addition, the **.rtbBtn**, **.rtbDropDown**, or **.rtbSplBtn** class identifies the type of toolbar item. The LI element also gets classes applied based on the state of the item. These include **.rtbChecked**, **.rtbDisabled**, **.rtbItemFocused**, **.rtbItemHovered**, **.rtbDropDownExpanded**, and **.rtbSplBtnExpanded**. - -Inside the LI element for an item in the toolbar is the A element for the button: - -````HTML -     - - - - - - - - -```` - -The A element has the **.rtbWrap** class applied. If you assign a value to the CssClass or style properties of a button, these are applied at this level as well. Inside the element are three nested SPAN elements, which the skin can use to achieve intricate effects on the shape of buttons. These have the **.rtbOut**, **.rtbMid**, and **.rtbIn** classes applied, as shown above. - -## RadToolBarButton - -The content of **RadToolBarButton** can include both an image and a text label: - -````HTML - -Cut -```` - - -The image is rendered as an IMG element with the **.rtbIcon** class applied. The text label is rendered as another SPAN element with the **.rtbText** class applied. - -## RadToolBarDropDown - -The content of **RadToolBarDropDown** can include an image and a label, as well as the drop-down arrow: - -````HTML - -Colors - -```` - -As with **RadToolBarButton**, the image gets the **.rtbIcon** class applied and the text gets the **.rtbText** class applied. The drop-down arrow is a SPAN tag with the **.rtbChoiceArrow** class applied. - -## RadToolBarSplitButton - -The content of **RadToolBarSplitButton** contains two SPAN elements: one for the button portion, and another for the drop-down arrow. The image and text label go inside the first SPAN: - -````HTML - - - Left Justify - - -```` - - -The SPAN for the button portion gets the **.rtbSplBtnActivator** class applied. As with **RadToolBarDropDown**, the drop-down arrow gets the **.rtbChoiceArrow** class applied. Inside the SPAN for the button portion, the label and image are rendered just like with other toolbar items. - -## Drop-down lists - -Drop-down lists are rendered as a DIV element immediately after the A element for the drop-down or split button: - -````HTML - -```` - -The first DIV for the drop-down has the **.rtbSlide** class applied. This is used for animation effects and can be ignored. Inside that is the main DIV for the drop-down list. It has the **RadToolBarDropDown** and **RadToolBarDropDown_Green** classes applied. The RadToolBarDropDown class is applied regardless of the skin, and defines the basic presentation for toolbar drop down lists common to all skins. The **RadToolBarDropDown_Green** class is applied because the **Skin** property is set to "Green". - -Inside the DIV for the drop-down is a UL element with the **.rtbGroup** and **.rtbActive** classes applied. The items in this list are rendered like the buttons in the toolbar, but without the three nested SPAN elements that are used to style the "button" appearance. (the **.rtbBtn** class is also omitted). - -## Separators - -Separators in drop-down lists are rendered as LI elements: - -````HTML -
  • _
    • -```` - - -The LI element for a separator has the **.rtbSeparator** class applied. Note that the text of the separator is rendered as a SPAN element. The reason that the text does not appear is that most skins map the **.rtbSeparator .rtbText** selector to "display: none" to hide the text. - -# See Also - - * [Skins]({%slug toolbar/appearance-and-styling/skins%}) - - * [Setting the CSS Class of Buttons]({%slug toolbar/appearance-and-styling/setting-the-css-class-of-buttons%}) +--- +title: Understanding the Skin CSS File +page_title: Understanding the Skin CSS File - RadToolBar +description: Check our Web Forms article about Understanding the Skin CSS File. +slug: toolbar/appearance-and-styling/understanding-the-skin-css-file +tags: understanding,the,skin,css,file +published: True +position: 6 +--- + +# Understanding the Skin CSS File + + + +Styles for RadControls are defined using Cascading Style Sheet (CSS) syntax. Each style consists of a selector that identifies an HTML element to be styled, and property/value pairs that describe each of the style specifics, e.g. color, padding, margins, etc. For example, the ".RadToolBar_Green_Horizontal" style shown below sets the background color of the toolbar: + +````ASPNET +.RadToolBar_Green_Horizontal{ background: #90cc90;} +```` + + +See the [CSS Skin FileSelectors]({%slug toolbar/appearance-and-styling/css-skin-file-selectors%}) topic for more information on the specific CSS selectors used for **RadToolBar** skins. + +Each style maps to a "class" attribute in an HTML tag. For example, consider the excerpt from the HTML rendering of a toolbar shown below: + +````HTML +
    + +
    +```` + + +The control is rendered as a DIV element with the classes "**RadToolBar RadToolBar_Horizontal RadToolBar_Green RadToolBar_Green_Horizontal**". The **RadToolBar** and **RadToolBar_Horizontal** classes are always applied. They define the basic presentation of the toolbar which is common for all skins. The **RadToolBar_Green** and **RadToolBar_Green_Horizontal** classes are applied because the **Skin** property of the toolbar is set to "Green". + +>note If you set the **Style** or **CssClass** property of the toolbar, those settings are applied to this outer DIV element as well. +> + + +## Tool Bar element + +Immediately inside the outer DIV tag for the toolbar (shown above), the rendered toolbar has three more nested DIV elements: + +````HTML +
    +
    +
    + +
    +
    +
    +```` + +These classes are available for skins to achieve intricate effects in the shape of the toolbar. Most skin CSS files use these classes to apply background images to create the rounded edges of the toolbar. + +Inside the three nested DIV tags, the toolbar uses an unordered list (LI) tag to manage the layout of the buttons in the toolbar: + +````HTML + +```` + +This UL tag always has the **.rtbUL** class applied. + +## Tool Bar Items + +Each item in the toolbar is an LI element inside the UL tag: + +````HTML +
  • + +
    • +
  • + +
    • +
  • + +
    • +```` + +The LI element always has the **.rtbItem** class applied.In addition, the **.rtbBtn**, **.rtbDropDown**, or **.rtbSplBtn** class identifies the type of toolbar item. The LI element also gets classes applied based on the state of the item. These include **.rtbChecked**, **.rtbDisabled**, **.rtbItemFocused**, **.rtbItemHovered**, **.rtbDropDownExpanded**, and **.rtbSplBtnExpanded**. + +Inside the LI element for an item in the toolbar is the A element for the button: + +````HTML + + + + + + + + + +```` + +The A element has the **.rtbWrap** class applied. If you assign a value to the CssClass or style properties of a button, these are applied at this level as well. Inside the A element are three nested SPAN elements, which the skin can use to achieve intricate effects on the shape of buttons. These have the **.rtbOut**, **.rtbMid**, and **.rtbIn** classes applied, as shown above. + +## RadToolBarButton + +The content of **RadToolBarButton** can include both an image and a text label: + +````HTML + +Cut +```` + + +The image is rendered as an IMG element with the **.rtbIcon** class applied. The text label is rendered as another SPAN element with the **.rtbText** class applied. + +## RadToolBarDropDown + +The content of **RadToolBarDropDown** can include an image and a label, as well as the drop-down arrow: + +````HTML + +Colors + +```` + +As with **RadToolBarButton**, the image gets the **.rtbIcon** class applied and the text gets the **.rtbText** class applied. The drop-down arrow is a SPAN tag with the **.rtbChoiceArrow** class applied. + +## RadToolBarSplitButton + +The content of **RadToolBarSplitButton** contains two SPAN elements: one for the button portion, and another for the drop-down arrow. The image and text label go inside the first SPAN: + +````HTML + + + Left Justify + + +```` + + +The SPAN for the button portion gets the **.rtbSplBtnActivator** class applied. As with **RadToolBarDropDown**, the drop-down arrow gets the **.rtbChoiceArrow** class applied. Inside the SPAN for the button portion, the label and image are rendered just like with other toolbar items. + +## Drop-down lists + +Drop-down lists are rendered as a DIV element immediately after the A element for the drop-down or split button: + +````HTML + +```` + +The first DIV for the drop-down has the **.rtbSlide** class applied. This is used for animation effects and can be ignored. Inside that is the main DIV for the drop-down list. It has the **RadToolBarDropDown** and **RadToolBarDropDown_Green** classes applied. The RadToolBarDropDown class is applied regardless of the skin, and defines the basic presentation for toolbar drop down lists common to all skins. The **RadToolBarDropDown_Green** class is applied because the **Skin** property is set to "Green". + +Inside the DIV for the drop-down is a UL element with the **.rtbGroup** and **.rtbActive** classes applied. The items in this list are rendered like the buttons in the toolbar, but without the three nested SPAN elements that are used to style the "button" appearance. (the **.rtbBtn** class is also omitted). + +## Separators + +Separators in drop-down lists are rendered as LI elements: + +````HTML +
  • _
    • +```` + + +The LI element for a separator has the **.rtbSeparator** class applied. Note that the text of the separator is rendered as a SPAN element. The reason that the text does not appear is that most skins map the **.rtbSeparator .rtbText** selector to "display: none" to hide the text. + +# See Also + + * [Skins]({%slug toolbar/appearance-and-styling/skins%}) + + * [Setting the CSS Class of Buttons]({%slug toolbar/appearance-and-styling/setting-the-css-class-of-buttons%}) diff --git a/controls/treeview/load-on-demand/tutorial-on-web-service-binding.md b/controls/treeview/load-on-demand/tutorial-on-web-service-binding.md index deef1077b8..c33d6613d3 100644 --- a/controls/treeview/load-on-demand/tutorial-on-web-service-binding.md +++ b/controls/treeview/load-on-demand/tutorial-on-web-service-binding.md @@ -1,104 +1,104 @@ ---- -title: Tutorial on Web Service Binding -page_title: Tutorial on Web Service Binding - RadTreeView -description: Check our Web Forms article about Tutorial on Web Service Binding. -slug: treeview/load-on-demand/tutorial-on-web-service-binding -tags: tutorial,on,web,service,binding -published: True -position: 3 ---- - -# Tutorial on Web Service Binding - - - -## - -The following tutorial demonstrates how to create a web service that can be consumed by the **RadTreeView** load-on-demand feature. - - ->caption - -![RadTreeView Web Service Tutorial](images/treeview_loadondemandwebservicetut03.png) - -1. Create an AJAX-Enabled Web Site by selecting the Visual Studio menu **File | New | Web Site.** - -1. Select the **ASP.NET AJAX-Enabled Web Site** option, set the **Location** to **File System** and enter a path for the web site. Click OK to close the New Web Site dialog. -![RadTreeView Web Service Tutorial](images/treeview_loadondemandwebservicetut01.png) - -1. Drop a **RadTreeView** control from the Toolbox to the default page. - ````ASPNET - - - - - - - - - - - - - - - -```` - - -1. In the Solution Explorer, right click the project and select **Add ASP.NET Folder | App_Code** from the context menu. - -1. In the Solution Explorer, right click the project and select **Add New Item** from the context menu. From the **Add New Item** dialog Select **Web Service,** name the service "ProductCategories.asmx" and click **Add** to close the dialog. -![RadTreeView Web Service Tutorial](images/treeview_loadondemandwebservicetut02.png) - -1. In Solution Explorer, locate ProductCategories.cs in the App_Code folder. Replace the code with the code below. - ````C# -public RadTreeNodeData[] GetTreeViewCategories(RadTreeNodeData node, object context) -{ - node.Text; //returns the node's text - node.Value; //returns node's value - - DataTable productCategories = GetProductCategories(node.Value); - List result = new List(); - foreach (DataRow row in productCategories.Rows) - { - RadTreeNodeData itemData = new RadTreeNodeData(); - itemData.Text = row["Title"].ToString(); - itemData.Value = row["CategoryId"].ToString(); - if (Convert.ToInt32(row["ChildrenCount"]) > 0) - { - itemData.ExpandMode = TreeNodeExpandMode.WebService; - } - result.Add(itemData); - } - return result.ToArray(); -} -```` - ````VB.NET -Public Function GetTreeViewCategories(ByVal node As RadTreeNodeData, ByVal context As Object) As RadTreeNodeData() - - node.Text 'returns the node's text - node.Value 'returns node's value - - Dim productCategories As DataTable = GetProductCategories(node.Value) - Dim result As New List(Of RadTreeNodeData)() - For Each row As DataRow In productCategories.Rows - Dim itemData As New RadTreeNodeData() - itemData.Text = row("Title").ToString() - itemData.Value = row("CategoryId").ToString() - If Convert.ToInt32(row("ChildrenCount")) > 0 Then - itemData.ExpandMode = TreeNodeExpandMode.WebService - End If - result.Add(itemData) - Next - Return result.ToArray() -End Function -```` - - ->note You can access the **Text** and **Value** of the node, which is being expanded, from the **RadTreeNodeData** parameter passed to the web method. -> - -1. In Solution Explorer, right click the default page and select **Set as Start Page** from the context menu. - -1. Press F5 to run the web site. Click OK to enable debugging. +--- +title: Tutorial on Web Service Binding +page_title: Tutorial on Web Service Binding - RadTreeView +description: Check our Web Forms article about Tutorial on Web Service Binding. +slug: treeview/load-on-demand/tutorial-on-web-service-binding +tags: tutorial,on,web,service,binding +published: True +position: 3 +--- + +# Tutorial on Web Service Binding + + + +## + +The following tutorial demonstrates how to create a web service that can be consumed by the **RadTreeView** load-on-demand feature. + + +>caption + +![RadTreeView Web Service Tutorial](images/treeview_loadondemandwebservicetut03.png) + +1. Create an AJAX-Enabled Web Site by selecting the Visual Studio menu **File | New | Web Site.** + +1. Select the **ASP.NET AJAX-Enabled Web Site** option, set the **Location** to **File System** and enter a path for the web site. Click OK to close the New Web Site dialog. +![RadTreeView Web Service Tutorial](images/treeview_loadondemandwebservicetut01.png) + +1. Drop a **RadTreeView** control from the Toolbox to the default page. + ````ASPNET + + + + + + + + + + + + + + + + ```` + + +1. In the Solution Explorer, right click the project and select **Add ASP.NET Folder | App_Code** from the context menu. + +1. In the Solution Explorer, right click the project and select **Add New Item** from the context menu. From the **Add New Item** dialog Select **Web Service,** name the service "ProductCategories.asmx" and click **Add** to close the dialog. +![RadTreeView Web Service Tutorial](images/treeview_loadondemandwebservicetut02.png) + +1. In Solution Explorer, locate ProductCategories.cs in the App_Code folder. Replace the code with the code below. + ````C# + public RadTreeNodeData[] GetTreeViewCategories(RadTreeNodeData node, object context) + { + node.Text; //returns the node's text + node.Value; //returns node's value + + DataTable productCategories = GetProductCategories(node.Value); + List result = new List(); + foreach (DataRow row in productCategories.Rows) + { + RadTreeNodeData itemData = new RadTreeNodeData(); + itemData.Text = row["Title"].ToString(); + itemData.Value = row["CategoryId"].ToString(); + if (Convert.ToInt32(row["ChildrenCount"]) > 0) + { + itemData.ExpandMode = TreeNodeExpandMode.WebService; + } + result.Add(itemData); + } + return result.ToArray(); + } + ```` + ````VB.NET + Public Function GetTreeViewCategories(ByVal node As RadTreeNodeData, ByVal context As Object) As RadTreeNodeData() + + node.Text 'returns the node's text + node.Value 'returns node's value + + Dim productCategories As DataTable = GetProductCategories(node.Value) + Dim result As New List(Of RadTreeNodeData)() + For Each row As DataRow In productCategories.Rows + Dim itemData As New RadTreeNodeData() + itemData.Text = row("Title").ToString() + itemData.Value = row("CategoryId").ToString() + If Convert.ToInt32(row("ChildrenCount")) > 0 Then + itemData.ExpandMode = TreeNodeExpandMode.WebService + End If + result.Add(itemData) + Next + Return result.ToArray() + End Function + ```` + + +>note You can access the **Text** and **Value** of the node, which is being expanded, from the **RadTreeNodeData** parameter passed to the web method. +> + +1. In Solution Explorer, right click the default page and select **Set as Start Page** from the context menu. + +1. Press F5 to run the web site. Click OK to enable debugging. diff --git a/controls/treeview/migrating-from-radtreeview-for-asp.net-to-asp.net-ajax.md b/controls/treeview/migrating-from-radtreeview-for-asp.net-to-asp.net-ajax.md index a4ec27d43c..598d919ccc 100644 --- a/controls/treeview/migrating-from-radtreeview-for-asp.net-to-asp.net-ajax.md +++ b/controls/treeview/migrating-from-radtreeview-for-asp.net-to-asp.net-ajax.md @@ -1,248 +1,248 @@ ---- -title: Migrating from RadTreeView for ASP.NET to ASP.NET AJAX -page_title: Migrating from RadTreeView for ASP.NET to ASP.NET AJAX - RadTreeView -description: Check our Web Forms article about Migrating from RadTreeView for ASP.NET to ASP.NET AJAX. -slug: treeview/migrating-from-radtreeview-for-asp.net-to-asp.net-ajax -tags: migrating,from,radtreeview,for,asp.net,to,asp.net,ajax -published: True -position: 4 ---- - -# Migrating from RadTreeView for ASP.NET to ASP.NET AJAX - - - -**RadTreeView for ASP.NET AJAX** contains a number of changes from moving to the ASP.NET Ajax framework and to the Telerik.Web.UI suite.These changes are listed below: - -## Client-Side Changes - - - -### RadTreeView - - - - -| RadTreeView Client-Side Object - "Classic" | RadTreeView Client-Side Object for ASP.NET AJAX | -| ------ | ------ | -||| -| **Methods** || -|FindNodeByText|findNodeByText()| -|FindNodeByValue|findNodeByValue()| -|FindNodeByAttribute|findNodeByAttribute()| -|GetSelectedNodes|get_selectedNodes()| -|UnSelectAllNodes|unselectAllNodes()| -|UpdateState|N/A (no longer required)| -|HideContextMenu|N/A (other API will be provided for Context Menu handling)| -||| -| **Properties** || -|Nodes|get_nodes()The return value is no longer an Array. The return value is now a Telerik.Web.UI.RadTreeNodeCollection object.Enumerating Nodes:| -|AllNodes|get_allNodes()The return value is Array.| -|ID|get_id()| -|SelectedNode|get_selectedNode()| - - - -### RadTreeNode - - - - -| RadTreeNode Client-Side Object - "Classic" | RadTreeNode Client-Side Object for ASP.NET AJAX | -| ------ | ------ | -||| -| **Methods** || -|Prev|get_previousNode()| -|Next|get_nextNode()| -|Expand|set_expanded(true) or expand()| -|Collapse|set_expanded(false) or collapse()| -|Toggle|toggle()| -|Highlight|highlight()| -|Select|set_selected(true) or select()| -|UnSelect|set_selected(false) or unselect()| -|Enable|set_enabled(true) or enable()| -|Disable|set_enabled(false) or disable()| -|Check|set_checked(true) or check()| -|UnCheck|set_checked(false) or uncheck()| -|StartEdit|startEdit()| -|EndEdit|endEdit()| -|CheckElement|get_checkBoxElement()| -|ScrollIntoView|scrollIntoView()| -|ImageElement|get_imageElement()| -|TextElement|get_textElement()| -||get_contentElement()Returns an HTML DOM element (a
  • tag) that represents a Tree Node.| -| **Properties** || -|Text|get_text()| -|Value|get_value()| -|Category|get_category()| -|Enabled|get_enabled()| -|Expanded|get_expanded()| -|Checked|get_checked()| -|Selected|get_selected()| -|Nodes|get_nodes()| -|Parent|get_parent()This method will return the RadTreeView if the Node is root Node.| -|TreeView|get_treeView()| -|Attributes|get_attributes(), getAttribute() and setAttribute()| - - - -### RadTreeNodeCollection New Methods - -See [RadTreeNodeCollection Object]({%slug treeview/client-side-programming/objects/radtreenodecollection%}) for more details. - - - - -| RadTreeNodeCollection Client-Side Object for ASP.NET AJAX | -| ------ | -|| -|add| -|insert| -|remove| -|removeAt| -|get_count| -|getNode| -|indexOf| - - - -## Server-Side Changes - - - -### RadTreeView Changes - - - - -| RadTreeView - "Classic" | RadTreeView for ASP.NET AJAX | -| ------ | ------ | -||| -| **Properties** || -|AfterClientFocus|OnClientFocused| -|BeforeClientContextMenu|OnClientContextMenuShowing| -|BeforeClientClick|OnClientNodeClicking| -|AfterClientClick|OnClientNodeClicked| -|AfterClientCallBackError|OnClientCallbackError| -|BeforeClientHighlight|OnClientMouseOver| -|AfterClientHighlight|OnClientMouseOver| -|BeforeClientDoubleClick|OnClientDoubleClicking| -|AfterClientMouseOut|OnClientMouseOut| -|AfterClientEdit|OnClientNode| -|BeforeClientDrop|OnClientNodeDropping| -|AfterClientDrop|OnClientNodeDropped| -|BeforeClientContextClick|OnClientContextClicking| -|BeforeClientCheck|OnClientNodeChecking| -|AfterClientCheck|OnClientNodeChecked| -|BeforeClientDrag|OnClientNodeDragStart| -|AfterClientMove|OnClientNodeDragging| -|AppendDataBoundNodes|AppendDataBoundItems| -|NodeBound|NodeDataBound| -||| -| **Types** || -|LoadingMessagePosition|TreeViewLoadingStatusPosition| - - - -### RadTreeView Deleted Methods and Properties - - - - -| Deleted Method or Property | Description | -| ------ | ------ | -||| -|ContentFile|Use the LoadContentFile method instead.| -|AjaxUrl|| -|ContextMenuContentFile|Replaced by new[context menus]({%slug treeview/context-menus/overview%})| -|AutoPostBack|Postback appears as soon as you hook on any server event requiring postback| -|AutoPostBackOnCheck|Subscribing to the NodeCheck event will enable postback for checking operations| -|GetContextMenusXml|Replaced by new[context menus]({%slug treeview/context-menus/overview%})| -|LoadContextMenusXmlString|Replaced by new[context menus]({%slug treeview/context-menus/overview%})| -|OnClientNodeToggling / Toggled|Replaced by OnClientNodeExpanding, OnClientNodeExpanded, OnClientNodeCollapsing, OnClientNodeCollapsed events| -|SSL|Treeview output is SSL compliant by default| -|ImagesBaseDir|The user would specify the whole path| -|RetainScrollPosition|This feature is on by default| -|IsCallback|Use Page.IsCallBack instead| -|LoadingMessageCssClass|Now controlled by the skin css styles| -|AfterClientFocus|Use the 'onfocus' attribute for the same purpose.| - -### RadTreeView Changed Return Types - - ->caption   - -| Changed Return Type for Method | Description | -| ------ | ------ | -||| -|GetAllNodes|Returns IList instead of ArrayList| -|CheckedNodes|Returns IList instead of ArrayList| -|SelectedNodes|Returns IList instead of ArrayList| - - - -### RadTreeViewEventHandler - - - -RadTreeViewEventHandler has been split into other delegates: - -1. **RadTreeViewEventHandler** is used by the following events: - * NodeClick - * NodeDataBound - * NodeCreated - * NodeExpand - * NodeCollapse - * NodeCheck - -1. **RadTreeViewDragDropEventHandler** is used only by the NodeDrop event - -1. **RadTreeViewEditEventHandler** is used only by the NodeEdit event - - - -### RadTreeNode Changes - - - - ->caption   - -| RadTreeNode - "Classic" | RadTreeNode for ASP.NET AJAX | -| ------ | ------ | -||| -| **Properties** || -|CssClassSelect|SelectedCssClass| -|ImageExpandedUrl|ExpandedImageUrl| -|Parent|ParentNode| -|EditEnabled|AllowEdit| -|DragEnabled|AllowDrag| -|DropEnabled|AllowDrop| - - - -### RadTreeNodeEventArgs - - - -That class has been split into other classes: - -1. **RadTreeNodeEventArgs** contains only one property - Node. It is used by the following events: - * NodeClick - * NodeDataBound - * NodeCreated - * NodeExpand - * NodeCollapse - * NodeCheck - -1. **RadTreeNodeDragDropEventArgs** is used solely by the NodeDrop event. It contains the following properties: - * SourceDragNode - * DestDragNode - * DropPosition - * HtmlElementID - -1. **RadTreeNodeEditEventArgs** is used solely by the NodeEdit event. It contains the following properties - * Node - * Text - - +--- +title: Migrating from RadTreeView for ASP.NET to ASP.NET AJAX +page_title: Migrating from RadTreeView for ASP.NET to ASP.NET AJAX - RadTreeView +description: Check our Web Forms article about Migrating from RadTreeView for ASP.NET to ASP.NET AJAX. +slug: treeview/migrating-from-radtreeview-for-asp.net-to-asp.net-ajax +tags: migrating,from,radtreeview,for,asp.net,to,asp.net,ajax +published: True +position: 4 +--- + +# Migrating from RadTreeView for ASP.NET to ASP.NET AJAX + + + +**RadTreeView for ASP.NET AJAX** contains a number of changes from moving to the ASP.NET Ajax framework and to the Telerik.Web.UI suite.These changes are listed below: + +## Client-Side Changes + + + +### RadTreeView + + + + +| RadTreeView Client-Side Object - "Classic" | RadTreeView Client-Side Object for ASP.NET AJAX | +| ------ | ------ | +||| +| **Methods** || +|FindNodeByText|findNodeByText()| +|FindNodeByValue|findNodeByValue()| +|FindNodeByAttribute|findNodeByAttribute()| +|GetSelectedNodes|get_selectedNodes()| +|UnSelectAllNodes|unselectAllNodes()| +|UpdateState|N/A (no longer required)| +|HideContextMenu|N/A (other API will be provided for Context Menu handling)| +||| +| **Properties** || +|Nodes|get_nodes()The return value is no longer an Array. The return value is now a Telerik.Web.UI.RadTreeNodeCollection object.Enumerating Nodes:``| +|AllNodes|get_allNodes()The return value is Array.| +|ID|get_id()| +|SelectedNode|get_selectedNode()| + + + +### RadTreeNode + + + + +| RadTreeNode Client-Side Object - "Classic" | RadTreeNode Client-Side Object for ASP.NET AJAX | +| ------ | ------ | +||| +| **Methods** || +|Prev|get_previousNode()| +|Next|get_nextNode()| +|Expand|set_expanded(true) or expand()| +|Collapse|set_expanded(false) or collapse()| +|Toggle|toggle()| +|Highlight|highlight()| +|Select|set_selected(true) or select()| +|UnSelect|set_selected(false) or unselect()| +|Enable|set_enabled(true) or enable()| +|Disable|set_enabled(false) or disable()| +|Check|set_checked(true) or check()| +|UnCheck|set_checked(false) or uncheck()| +|StartEdit|startEdit()| +|EndEdit|endEdit()| +|CheckElement|get_checkBoxElement()| +|ScrollIntoView|scrollIntoView()| +|ImageElement|get_imageElement()| +|TextElement|get_textElement()| +||get_contentElement()Returns an HTML DOM element (a <LI> tag) that represents a Tree Node.| +| **Properties** || +|Text|get_text()| +|Value|get_value()| +|Category|get_category()| +|Enabled|get_enabled()| +|Expanded|get_expanded()| +|Checked|get_checked()| +|Selected|get_selected()| +|Nodes|get_nodes()| +|Parent|get_parent()This method will return the RadTreeView if the Node is root Node.| +|TreeView|get_treeView()| +|Attributes|get_attributes(), getAttribute() and setAttribute()| + + + +### RadTreeNodeCollection New Methods + +See [RadTreeNodeCollection Object]({%slug treeview/client-side-programming/objects/radtreenodecollection%}) for more details. + + + + +| RadTreeNodeCollection Client-Side Object for ASP.NET AJAX | +| ------ | +|| +|add| +|insert| +|remove| +|removeAt| +|get_count| +|getNode| +|indexOf| + + + +## Server-Side Changes + + + +### RadTreeView Changes + + + + +| RadTreeView - "Classic" | RadTreeView for ASP.NET AJAX | +| ------ | ------ | +||| +| **Properties** || +|AfterClientFocus|OnClientFocused| +|BeforeClientContextMenu|OnClientContextMenuShowing| +|BeforeClientClick|OnClientNodeClicking| +|AfterClientClick|OnClientNodeClicked| +|AfterClientCallBackError|OnClientCallbackError| +|BeforeClientHighlight|OnClientMouseOver| +|AfterClientHighlight|OnClientMouseOver| +|BeforeClientDoubleClick|OnClientDoubleClicking| +|AfterClientMouseOut|OnClientMouseOut| +|AfterClientEdit|OnClientNode| +|BeforeClientDrop|OnClientNodeDropping| +|AfterClientDrop|OnClientNodeDropped| +|BeforeClientContextClick|OnClientContextClicking| +|BeforeClientCheck|OnClientNodeChecking| +|AfterClientCheck|OnClientNodeChecked| +|BeforeClientDrag|OnClientNodeDragStart| +|AfterClientMove|OnClientNodeDragging| +|AppendDataBoundNodes|AppendDataBoundItems| +|NodeBound|NodeDataBound| +||| +| **Types** || +|LoadingMessagePosition|TreeViewLoadingStatusPosition| + + + +### RadTreeView Deleted Methods and Properties + + + + +| Deleted Method or Property | Description | +| ------ | ------ | +||| +|ContentFile|Use the LoadContentFile method instead.| +|AjaxUrl|| +|ContextMenuContentFile|Replaced by new[context menus]({%slug treeview/context-menus/overview%})| +|AutoPostBack|Postback appears as soon as you hook on any server event requiring postback| +|AutoPostBackOnCheck|Subscribing to the NodeCheck event will enable postback for checking operations| +|GetContextMenusXml|Replaced by new[context menus]({%slug treeview/context-menus/overview%})| +|LoadContextMenusXmlString|Replaced by new[context menus]({%slug treeview/context-menus/overview%})| +|OnClientNodeToggling / Toggled|Replaced by OnClientNodeExpanding, OnClientNodeExpanded, OnClientNodeCollapsing, OnClientNodeCollapsed events| +|SSL|Treeview output is SSL compliant by default| +|ImagesBaseDir|The user would specify the whole path| +|RetainScrollPosition|This feature is on by default| +|IsCallback|Use Page.IsCallBack instead| +|LoadingMessageCssClass|Now controlled by the skin css styles| +|AfterClientFocus|Use the 'onfocus' attribute for the same purpose.| + +### RadTreeView Changed Return Types + + +>caption   + +| Changed Return Type for Method | Description | +| ------ | ------ | +||| +|GetAllNodes|Returns IList<RadTreeNode> instead of ArrayList| +|CheckedNodes|Returns IList<RadTreeNode> instead of ArrayList| +|SelectedNodes|Returns IList<RadTreeNode> instead of ArrayList| + + + +### RadTreeViewEventHandler + + + +RadTreeViewEventHandler has been split into other delegates: + +1. **RadTreeViewEventHandler** is used by the following events: + * NodeClick + * NodeDataBound + * NodeCreated + * NodeExpand + * NodeCollapse + * NodeCheck + +1. **RadTreeViewDragDropEventHandler** is used only by the NodeDrop event + +1. **RadTreeViewEditEventHandler** is used only by the NodeEdit event + + + +### RadTreeNode Changes + + + + +>caption   + +| RadTreeNode - "Classic" | RadTreeNode for ASP.NET AJAX | +| ------ | ------ | +||| +| **Properties** || +|CssClassSelect|SelectedCssClass| +|ImageExpandedUrl|ExpandedImageUrl| +|Parent|ParentNode| +|EditEnabled|AllowEdit| +|DragEnabled|AllowDrag| +|DropEnabled|AllowDrop| + + + +### RadTreeNodeEventArgs + + + +That class has been split into other classes: + +1. **RadTreeNodeEventArgs** contains only one property - Node. It is used by the following events: + * NodeClick + * NodeDataBound + * NodeCreated + * NodeExpand + * NodeCollapse + * NodeCheck + +1. **RadTreeNodeDragDropEventArgs** is used solely by the NodeDrop event. It contains the following properties: + * SourceDragNode + * DestDragNode + * DropPosition + * HtmlElementID + +1. **RadTreeNodeEditEventArgs** is used solely by the NodeEdit event. It contains the following properties + * Node + * Text + + diff --git a/controls/treeview/templates/accessing-controls-inside-templates.md b/controls/treeview/templates/accessing-controls-inside-templates.md index 9a0e7eba43..b50e9f09e9 100644 --- a/controls/treeview/templates/accessing-controls-inside-templates.md +++ b/controls/treeview/templates/accessing-controls-inside-templates.md @@ -1,57 +1,57 @@ ---- -title: Accessing Controls Inside Templates -page_title: Accessing Controls Inside Templates - RadTreeView -description: Check our Web Forms article about Accessing Controls Inside Templates. -slug: treeview/templates/accessing-controls-inside-templates -tags: accessing,controls,inside,templates -published: True -position: 5 ---- - -# Accessing Controls Inside Templates - -If your **RadTreeView** has Nodes with Templates that have embedded controls, you may want to access the properties of those embedded controls. To get a reference to the embedded control, locate the **Node** that has a Template, and use its **FindControl** server-side/**findControl** client-side method. - -For example, consider the following, very simple TreeView: - -````ASP.NET - - -
    - - -
    -     -     -```` - -To access the **RadDatePicker** in the Node Template, use the following code: - -Server-side access - -````C# -RadTreeNode node = RadTreeView1.Nodes[0]; -RadDatePicker datePicker = (RadDatePicker)node.FindControl("RadDatePicker1"); -```` -````VB -Dim node As RadTreeNode = RadTreeView1.Nodes(0) -Dim datePicker As RadDatePicker = DirectCast(node.FindControl("RadDatePicker1"), RadDatePicker) -```` - -Client-side access - -````JavaScript -var treeView = $find("<%= RadTreeView1.ClientID %>"); -var node = treeView.get_nodes().getNode(0); -var datePicker = node.findControl("RadDatePicker1"); -```` - -or - -````JavaScript -var datePicker = $find('<%= RadTreeView1.Nodes[0].FindControl("RadDatePicker1").ClientID %>'); -```` - -# See Also - - * [Overview]({%slug treeview/templates/overview%}) +--- +title: Accessing Controls Inside Templates +page_title: Accessing Controls Inside Templates - RadTreeView +description: Check our Web Forms article about Accessing Controls Inside Templates. +slug: treeview/templates/accessing-controls-inside-templates +tags: accessing,controls,inside,templates +published: True +position: 5 +--- + +# Accessing Controls Inside Templates + +If your **RadTreeView** has Nodes with Templates that have embedded controls, you may want to access the properties of those embedded controls. To get a reference to the embedded control, locate the **Node** that has a Template, and use its **FindControl** server-side/**findControl** client-side method. + +For example, consider the following, very simple TreeView: + +````ASP.NET + + +
    + + +
    +     +     +```` + +To access the **RadDatePicker** in the Node Template, use the following code: + +Server-side access + +````C# +RadTreeNode node = RadTreeView1.Nodes[0]; +RadDatePicker datePicker = (RadDatePicker)node.FindControl("RadDatePicker1"); +```` +````VB +Dim node As RadTreeNode = RadTreeView1.Nodes(0) +Dim datePicker As RadDatePicker = DirectCast(node.FindControl("RadDatePicker1"), RadDatePicker) +```` + +Client-side access + +````JavaScript +var treeView = $find("<%= RadTreeView1.ClientID %>"); +var node = treeView.get_nodes().getNode(0); +var datePicker = node.findControl("RadDatePicker1"); +```` + + or + +````JavaScript +var datePicker = $find('<%= RadTreeView1.Nodes[0].FindControl("RadDatePicker1").ClientID %>'); +```` + +# See Also + + * [Overview]({%slug treeview/templates/overview%}) diff --git a/docs-builder.yml b/docs-builder.yml new file mode 100644 index 0000000000..6736ff64a5 --- /dev/null +++ b/docs-builder.yml @@ -0,0 +1,1949 @@ +top-navigation-product: asp-net-ajax +path-prefix: /products/aspnet-ajax/documentation +default-title-prefix: Telerik Web Forms + +primary-color: "#27A306" +product-id: 561 +product-code: RCAJAX +product-name: Telerik UI for ASP.NET AJAX +product-url: https://www.telerik.com/products/aspnet-ajax.aspx +product-trial-url: https://www.telerik.com/try/ui-for-asp.net-ajax +contribute-url: https://github.com/telerik/ajax-docs/edit/master +search-engine-id: 85d0502fb709b472f +avatar-path: ./images/avatar-ninja.svg +no-results-image-path: ./images/ninja-no-results.svg +enable-tabbed-code-blocks: true +pdf-cover-png-path: ./images/pdf-cover.png +img-max-width: 100% +table-layout: fixed + +cta-overview: The @Subject is part of @ProductLink, a professional grade UI library with 120+ components for building modern and feature-rich applications. To try it out sign up for a free 30-day trial. +cta-intro: "@ProductLink is a professional grade UI library with 120+ components for building modern and feature-rich applications. To try it out sign up for a free 30-day trial." + +meta: + "*ziplibrary/features": + title: Features + position: 4 + "*wordsprocessing/concepts/fields": + title: Fields + position: 0 + "*wordsprocessing/formats-and-conversion/plain-text": + title: Plain text + position: 5 + "*wordsprocessing/formats-and-conversion/pdf": + title: Pdf + position: 4 + "*wordsprocessing/formats-and-conversion/html": + title: Html + position: 3 + "*wordsprocessing/formats-and-conversion/rtf": + title: Rtf + position: 2 + "*wordsprocessing/formats-and-conversion/docx": + title: Docx + position: 1 + "*wordsprocessing/concepts": + title: Concepts + position: 7 + "*wordsprocessing/editing": + title: Editing + position: 6 + "*wordsprocessing/formats-and-conversion": + title: Formats and Conversion + position: 5 + "*wordsprocessing/model": + title: Model + position: 4 + "*wizard/structure": + title: Structure + position: 3 + "*window/alert,-confirm,-prompt-dialogs": + title: Alert, Confirm, Prompt Dialogs + position: 5 + "*upload/localization": + title: Localization + position: 10 + "*upload/validation": + title: Validation + position: 8 + "*upload/uploading-files": + title: Uploading Files + position: 7 + "*treeview/!not-referenced-topics!": + title: "!Not Referenced topics!" + position: 22 + "*treeview/application-scenarios/general": + title: General + position: 5 + "*treeview/application-scenarios/client-side-programming": + title: Client-side Programming + position: 4 + "*treeview/application-scenarios/server-side-programming": + title: Server-side Programming + position: 3 + "*treeview/application-scenarios/checkboxes": + title: CheckBoxes + position: 2 + "*treeview/application-scenarios/context-menus": + title: Context Menus + position: 1 + "*treeview/application-scenarios/data-binding": + title: Data Binding + position: 0 + "*treeview/application-scenarios": + title: Application Scenarios + position: 20 + "*treeview/client-side-programming/objects": + title: Objects + position: 2 + "*treeview/web-pages": + title: Web Pages + position: 15 + "*treeview/drag-and-drop": + title: Drag and Drop + position: 14 + "*treeview/context-menus": + title: Context Menus + position: 13 + "*treeview/checkboxes/tri-state": + title: Tri-State + position: 3 + "*treeview/checkboxes": + title: CheckBoxes + position: 12 + "*treeview/custom-attributes": + title: Custom Attributes + position: 11 + "*treeview/radtreeview-nodes": + title: RadTreeView Nodes + position: 10 + "*treeview/load-on-demand": + title: Load On Demand + position: 9 + "*treeview/data-binding": + title: Data Binding + position: 8 + "*treeview/templates": + title: Templates + position: 7 + "*treemap/data-binding": + title: Data Binding + position: 4 + "*treemap/templates": + title: Templates + position: 3 + "*treelist/control-lifecycle": + title: Control Lifecycle + position: 10 + "*treelist/defining-structure": + title: Defining Structure + position: 9 + "*treelist/data-editing/updating-records": + title: Updating Records + position: 5 + "*treelist/data-editing/inserting-records": + title: Inserting Records + position: 4 + "*treelist/data-editing/column-editors": + title: Column Editors + position: 1 + "*treelist/data-editing/edit-mode": + title: Edit Mode + position: 0 + "*treelist/data-editing": + title: Data Editing + position: 8 + "*treelist/functionality/exporting/excel": + title: Excel + position: 3 + "*treelist/functionality/exporting/pdf": + title: PDF + position: 2 + "*treelist/functionality/exporting": + title: Exporting + position: 4 + "*treelist/functionality/selecting": + title: Selecting + position: 3 + "*treelist/functionality/scrolling/how-to": + title: How To + position: 2 + "*treelist/functionality/scrolling": + title: Scrolling + position: 2 + "*treelist/data-binding": + title: Data Binding + position: 6 + "*treelist/items": + title: Items + position: 5 + "*treelist/column": + title: Column + position: 4 + "*tooltip/client-side-programming/events/tooltipmanager-specific": + title: ToolTipManager Specific + position: 7 + "*tooltip/performance": + title: Performance + position: 6 + "*tooltip/radtooltipmanager": + title: RadToolTipManager + position: 5 + "*tooltip/radtooltip": + title: RadToolTip + position: 4 + "*toolbar/client-side-programming/objects": + title: Objects + position: 4 + "*toolbar/web-pages": + title: Web Pages + position: 11 + "*toolbar/templates": + title: Templates + position: 10 + "*toolbar/data-binding": + title: Data Binding + position: 8 + "*toolbar/radtoolbar-items": + title: RadToolBar Items + position: 7 + "*timepicker/performance": + title: Performance + position: 14 + "*timepicker/templates": + title: Templates + position: 8 + "*timeline/data-binding/server-side": + title: Server-side + position: 2 + "*timeline/data-binding": + title: Data Binding + position: 3 + "*tilelist/data-binding": + title: Data Binding + position: 4 + "*tilelist/tiles/client-side-programming/events/livetile-specific": + title: LiveTile Specific + position: 5 + "*tilelist/tiles/client-side-programming/events": + title: Events + position: 8 + "*tilelist/tiles/client-side-programming": + title: Client-side Programming + position: 12 + "*tilelist/tiles/server-side-programming/events": + title: Events + position: 1 + "*tilelist/tiles/server-side-programming": + title: Server-side Programming + position: 11 + "*tilelist/tiles/appearance-and-styling": + title: Appearance and Styling + position: 10 + "*tilelist/tiles/live-tile": + title: Live Tile + position: 6 + "*tilelist/tiles": + title: Tiles + position: 3 + "*textbox/how-to": + title: How to + position: 11 + "*textbox/client-side-programming": + title: Client-Side Programming + position: 10 + "*textbox/server-side-programming": + title: Server-Side Programming + position: 9 + "*textbox/accessibility-and-internationalization": + title: Accessibility and Internationalization + position: 8 + "*textbox/appearance-and-styling ": + title: Appearance and Styling + position: 7 + "*textbox/mobile-support/": + title: Mobile Support + position: 6 + "*textbox/features": + title: Features + position: 5 + "*textbox/design-time": + title: Design Time + position: 4 + "*tagcloud/data-binding": + title: Data Binding + position: 4 + "*tabstrip/client-side-programming/objects": + title: Objects + position: 1 + "*tabstrip/performance": + title: Performance + position: 12 + "*tabstrip/web-pages": + title: Web Pages + position: 11 + "*tabstrip/radmultipage": + title: RadMultiPage + position: 10 + "*tabstrip/tabs": + title: Tabs + position: 9 + "*tabstrip/data-binding": + title: Data Binding + position: 8 + "*tabstrip/templates": + title: Templates + position: 7 + "*stylesheetmanager/cdn-support": + title: CDN Support + position: 1 + "*spreadsheet/client-side-programming/objects": + title: Objects + position: 0 + "*spreadsheet/functionality/multilinecellediting": + title: Multiline Cell Editing + position: 7 + "*spreadsheet/functionality/formulas-and-functions": + title: Formulas and Functions + position: 6 + "*spreadsheet/functionality/validation": + title: Validation + position: 5 + "*spreadsheet/functionality/cellhyperlink": + title: Cell Hyperlink + position: 4 + "*spreadsheet/functionality/cellformat": + title: Cell Format + position: 3 + "*spreadsheet/functionality/filtermenu": + title: Filter Menu + position: 2 + "*spreadsheet/functionality/contextmenu": + title: Context Menu + position: 1 + "*spreadsheet/data-binding/providers": + title: Providers + position: 1 + "*spreadsheet/data-binding": + title: Data Binding + position: 3 + "*spreadsheet/structure": + title: Structure + position: 2 + "*spreadprocessing/features/styling": + title: Styling + position: 3 + "*spreadprocessing/features/protection": + title: Protection + position: 2 + "*spreadprocessing/features/formulas": + title: Formulas + position: 1 + "*spreadprocessing/features/fill-data-automatically": + title: Fill Data Automatically + position: 0 + "*spreadprocessing/formats-and-conversion/txt": + title: Txt + position: 5 + "*spreadprocessing/formats-and-conversion/csv": + title: Csv + position: 4 + "*spreadprocessing/formats-and-conversion/pdf": + title: Pdf + position: 3 + "*spreadprocessing/formats-and-conversion/xlsx": + title: Xlsx + position: 2 + "*spreadprocessing/features": + title: Features + position: 8 + "*spreadprocessing/formats-and-conversion": + title: Formats and Conversion + position: 7 + "*spreadprocessing/working-with-cells": + title: Working with Cells + position: 6 + "*spreadprocessing/working-with-rows-and-columns": + title: Working with Rows and Columns + position: 5 + "*spreadprocessing/working-with-worksheets": + title: Working with Worksheets + position: 4 + "*spreadprocessing/working-with-workbooks": + title: Working with Workbooks + position: 3 + "*splitter/sliding-zones": + title: Sliding Zones + position: 6 + "*splitter/panes": + title: Panes + position: 5 + "*splitter/layout": + title: Layout + position: 4 + "*spell/dictionaries": + title: Dictionaries + position: 7 + "*spell/configuration": + title: Configuration + position: 4 + "*socialshare/configuring-buttons": + title: Configuring Buttons + position: 5 + "*slider/client-side-programming/events/data-binding": + title: Data Binding + position: 11 + "*slider/data-binding": + title: Data Binding + position: 4 + "*sitemap/radsitemap-nodes": + title: RadSiteMap Nodes + position: 6 + "*sitemap/data-binding": + title: Data Binding + position: 5 + "*sitemap/templates": + title: Templates + position: 4 + "*sitemap/design-time/radsitemapdatasource": + title: RadSiteMapDataSource + position: 1 + "*sitemap/design-time/radsitemap": + title: RadSiteMap + position: 0 + "*searchbox/search-context/events": + title: Events + position: 3 + "*searchbox/search-context/data-binding": + title: Data Binding + position: 1 + "*searchbox/search-context": + title: Search Context + position: 6 + "*searchbox/data-binding": + title: Data Binding + position: 4 + "*searchbox/templates": + title: Templates + position: 3 + "*scriptmanager/cdn-support": + title: CDN Support + position: 8 + "*scheduler/performance": + title: Performance + position: 19 + "*scheduler/customizing-the-advanced-form": + title: Customizing the Advanced Form + position: 18 + "*scheduler/client-side-programming/properties-and-methods": + title: Properties and Methods + position: 0 + "*scheduler/web-service-binding": + title: Web Service Binding + position: 12 + "*scheduler/export/pdf": + title: PDF + position: 0 + "*scheduler/export": + title: Export + position: 11 + "*scheduler/data-binding/providers": + title: Providers + position: 7 + "*scheduler/data-binding": + title: Data Binding + position: 10 + "*scheduler/recurrence-editor/client-side-programming": + title: Client-side Programming + position: 3 + "*scheduler/recurrence-editor/server-side-programming": + title: Server-side Programming + position: 2 + "*scheduler/recurrence-editor/localization": + title: Localization + position: 1 + "*scheduler/recurrence-editor": + title: Recurrence Editor + position: 9 + "*scheduler/reminders": + title: Reminders + position: 8 + "*scheduler/context-menus": + title: Context Menus + position: 7 + "*scheduler/views": + title: Views + position: 6 + "*scheduler/usability": + title: Usability + position: 5 + "*checkboxlist/data-binding": + title: Data Binding + position: 14 + "*radiobuttonlist/data-binding": + title: Data Binding + position: 14 + "*rotator/data-binding": + title: Data Binding + position: 4 + "*ribbonbar/radribbonbar-items/ribbonbargallery": + title: RibbonBarGallery + position: 0 + "*ribbonbar/radribbonbar-items": + title: RadRibbonBar Items + position: 4 + "*ribbonbar/templates": + title: Templates + position: 3 + "*progressarea/localization": + title: Localization + position: 9 + "*pivotgrid/layouts": + title: Layouts + position: 8 + "*pivotgrid/totals": + title: Totals + position: 6 + "*pivotgrid/functionality/export": + title: Export + position: 5 + "*pivotgrid/functionality/paging": + title: Paging + position: 0 + "*pivotgrid/functionality": + title: Functionality + position: 5 + "*pivotgrid/fields": + title: Fields + position: 4 + "*pivotgrid/data-binding": + title: Data Binding + position: 3 + "*pdfviewer/processing": + title: Processing + position: 14 + "*pdfprocessing/howto": + title: How To + position: 100 + "*pdfprocessing/concepts": + title: Concepts + position: 7 + "*pdfprocessing/editing": + title: Editing + position: 6 + "*pdfprocessing/formats-and-conversion/pdf": + title: Pdf + position: 0 + "*pdfprocessing/formats-and-conversion": + title: Formats and Conversion + position: 5 + "*pdfprocessing/model": + title: Model + position: 4 + "*panelbar/web-pages": + title: Web Pages + position: 9 + "*panelbar/radpanelbar-items": + title: RadPanelBar Items + position: 8 + "*panelbar/data-binding": + title: Data Binding + position: 7 + "*panelbar/templates": + title: Templates + position: 6 + "*pagelayout/creating-responsive-design": + title: Creating Responsive Design + position: 3 + "*pagelayout/structure": + title: Structure + position: 4 + "*orgchart/data-binding": + title: Data Binding + position: 4 + "*orgchart/templates": + title: Templates + position: 2 + "*odatadatasource/client-side-programming/objects": + title: Objects + position: 0 + "*numerictextbox/how-to": + title: How to + position: 11 + "*numerictextbox/client-side-programming": + title: Client-Side Programming + position: 10 + "*numerictextbox/server-side-programming": + title: Server-Side Programming + position: 9 + "*numerictextbox/accessibility-and-internationalization": + title: Accessibility and Internationalization + position: 8 + "*numerictextbox/appearance-and-styling ": + title: Appearance and Styling + position: 7 + "*numerictextbox/mobile-support/": + title: Mobile Support + position: 6 + "*numerictextbox/features": + title: Features + position: 5 + "*numerictextbox/design-time": + title: Design Time + position: 4 + "*notification/setting-content": + title: Setting Content + position: 4 + "*navigation/client-side-programming/objects": + title: Objects + position: 1 + "*navigation/data-binding": + title: Data Binding + position: 6 + "*navigation/templates": + title: Templates + position: 5 + "*multiselect/data-binding": + title: Data Binding + position: 3 + "*menu/client-side-programming/objects": + title: Objects + position: 2 + "*menu/performance": + title: Performance + position: 14 + "*menu/context-menus": + title: Context Menus + position: 11 + "*menu/radmenu-items": + title: RadMenu Items + position: 10 + "*menu/templates": + title: Templates + position: 9 + "*menu/data-binding": + title: Data Binding + position: 7 + "*map/data-binding": + title: Data Binding + position: 4 + "*maskedtextbox/how-to": + title: How to + position: 10 + "*maskedtextbox/client-side-programming": + title: Client-Side Programming + position: 10 + "*maskedtextbox/server-side-programming": + title: Server-Side Programming + position: 9 + "*maskedtextbox/accessibility-and-internationalization": + title: Accessibility and Internationalization + position: 8 + "*maskedtextbox/appearance-and-styling ": + title: Appearance and Styling + position: 7 + "*maskedtextbox/mobile-support/": + title: Mobile Support + position: 6 + "*maskedtextbox/features": + title: Features + position: 5 + "*maskedtextbox/design-time": + title: Design Time + position: 4 + "*listview/client-side-programming/radlistview/methods": + title: Methods + position: 2 + "*listview/client-side-programming/radlistview/properties": + title: Properties + position: 1 + "*listview/client-side-programming/radlistview": + title: RadListView + position: 2 + "*listview/control-lifecycle": + title: Control Lifecycle + position: 11 + "*listview/defining-structure": + title: Defining Structure + position: 10 + "*listview/items": + title: Items + position: 9 + "*listview/templates": + title: Templates + position: 8 + "*listview/layouts": + title: Layouts + position: 7 + "*listview/data-editing/how-to": + title: How To + position: 4 + "*listview/data-editing": + title: Data Editing + position: 6 + "*listview/fuctionality/filtering": + title: Filtering + position: 4 + "*listview/fuctionality/grouping": + title: Grouping + position: 3 + "*listview/fuctionality/selecting": + title: Selecting + position: 2 + "*listview/fuctionality/sorting": + title: Sorting + position: 1 + "*listview/fuctionality/paging": + title: Paging + position: 0 + "*listview/fuctionality": + title: Fuctionality + position: 5 + "*listview/data-binding/client-side": + title: Client-side + position: 1 + "*listview/data-binding/server-side": + title: Server-side + position: 0 + "*listview/data-binding": + title: Data Binding + position: 4 + "*listbox/client-side-programming/objects": + title: Objects + position: 1 + "*listbox/templates": + title: Templates + position: 9 + "*listbox/radlistbox-items": + title: RadListBox Items + position: 8 + "*listbox/data-binding": + title: Data Binding + position: 6 + "*inputmanager/client-side-events": + title: Client-Side Events + position: 8 + "*inputmanager/server-side-events": + title: Server-Side Events + position: 7 + "*imagegallery/data-binding/server-side": + title: Server-side + position: 0 + "*imagegallery/data-binding": + title: Data Binding + position: 3 + "*imageeditor/troubleshooting/known-issues": + title: Known Issues + position: 0 + "*htmlchart/troubleshooting/known-issues": + title: Known Issues + position: 3 + "*htmlchart/functionality/axes": + title: Axes + position: 1 + "*htmlchart/functionality/clienttemplate": + title: ClientTemplate + position: 0 + "*htmlchart/data-binding": + title: Data Binding + position: 5 + "*htmlchart/chart-types": + title: Chart Types + position: 4 + "*htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart": + title: Migrating from RadChart to RadHtmlChart + position: 0 + "*grid/how-to/persisting-settings": + title: Persisting Settings + position: 8 + "*grid/how-to/hierarchy": + title: Hierarchy + position: 7 + "*grid/how-to/data-editing": + title: Data-Editing + position: 3 + "*grid/how-to/ajaxified-grid": + title: Ajaxified Grid + position: 2 + "*grid/how-to": + title: How To + position: 21 + "*grid/client-side-programming/events/events": + title: Events + position: 1 + "*grid/client-side-programming/events": + title: Events + position: 7 + "*grid/client-side-programming/gridcolumn-object/methods": + title: Methods + position: 2 + "*grid/client-side-programming/gridcolumn-object/properties": + title: Properties + position: 1 + "*grid/client-side-programming/gridcolumn-object": + title: GridColumn Object + position: 6 + "*grid/client-side-programming/griddataitem-object/methods": + title: Methods + position: 2 + "*grid/client-side-programming/griddataitem-object/properties": + title: Properties + position: 1 + "*grid/client-side-programming/griddataitem-object": + title: GridDataItem Object + position: 5 + "*grid/client-side-programming/gridtableview-object/collections": + title: Collections + position: 3 + "*grid/client-side-programming/gridtableview-object/methods": + title: Methods + position: 2 + "*grid/client-side-programming/gridtableview-object/properties": + title: Properties + position: 1 + "*grid/client-side-programming/gridtableview-object": + title: GridTableView Object + position: 4 + "*grid/client-side-programming/radgrid-object/methods": + title: Methods + position: 2 + "*grid/client-side-programming/radgrid-object/properties": + title: Properties + position: 1 + "*grid/client-side-programming/radgrid-object": + title: RadGrid Object + position: 3 + "*grid/client-side-programming": + title: Client-Side Programming + position: 20 + "*grid/server-side-programming": + title: Server-Side Programming + position: 19 + "*grid/control-lifecycle": + title: Control Lifecycle + position: 18 + "*grid/inheritance": + title: Inheritance + position: 17 + "*grid/ajaxified-radgrid/what-you-should-have-in-mind": + title: What You Should Have in Mind + position: 1 + "*grid/ajaxified-radgrid": + title: Ajaxified RadGrid + position: 16 + "*grid/visible-and-enabled-conventions": + title: Visible and Enabled Conventions + position: 15 + "*grid/asp.net-3.5-features": + title: ASP.NET 3.5 Features + position: 14 + "*grid/hierarchical-grid-types-and-load-modes/how-to": + title: How-to + position: 11 + "*grid/hierarchical-grid-types-and-load-modes": + title: Hierarchical Grid Types and Load Modes + position: 13 + "*grid/performance": + title: Performance + position: 12 + "*grid/mobile-support/mobile-rendering": + title: Mobile Rendering + position: 1 + "*grid/functionality/exporting/word-export": + title: Word Export + position: 4 + "*grid/functionality/exporting/excel-export": + title: Excel Export + position: 3 + "*grid/functionality/printing": + title: Printing + position: 7 + "*grid/functionality/exporting": + title: Exporting + position: 6 + "*grid/functionality/selecting/selecting-cells": + title: Selecting Cells + position: 2 + "*grid/functionality/selecting/selecting-rows": + title: Selecting Rows + position: 1 + "*grid/functionality/selecting": + title: Selecting + position: 5 + "*grid/functionality/filtering": + title: Filtering + position: 4 + "*grid/functionality/grouping/group-by-expressions": + title: Group-by Expressions + position: 1 + "*grid/functionality/grouping": + title: Grouping + position: 3 + "*grid/functionality/scrolling": + title: Scrolling + position: 2 + "*grid/functionality/sorting": + title: Sorting + position: 1 + "*grid/functionality/paging/changing-the-default-pager": + title: Changing the Default Pager + position: 4 + "*grid/functionality/paging": + title: Paging + position: 0 + "*grid/functionality": + title: Functionality + position: 11 + "*grid/accessing-values-and-controls/server-side": + title: Server Side + position: 2 + "*grid/accessing-values-and-controls/client-side": + title: Client Side + position: 1 + "*grid/accessing-values-and-controls": + title: Accessing Values and Controls + position: 10 + "*grid/rows": + title: Rows + position: 9 + "*grid/columns": + title: Columns + position: 8 + "*grid/data-editing/how-to": + title: How-to + position: 16 + "*grid/data-editing/commanditem": + title: CommandItem + position: 15 + "*grid/data-editing/delete-records": + title: Delete Records + position: 11 + "*grid/data-editing/validation": + title: Validation + position: 10 + "*grid/data-editing/insert-records": + title: Insert Records + position: 6 + "*grid/data-editing/update-records": + title: Update Records + position: 5 + "*grid/data-editing/grid-editors": + title: Grid Editors + position: 1 + "*grid/data-editing/edit-mode/batch-editing": + title: Batch Editing + position: 0 + "*grid/data-editing/edit-mode": + title: Edit Mode + position: 0 + "*grid/data-editing": + title: Data Editing + position: 7 + "*grid/data-binding/webservice-binding": + title: WebService Binding + position: 3 + "*grid/data-binding/server-side-binding/various-data-sources": + title: Various Data Sources + position: 3 + "*grid/data-binding/server-side-binding": + title: Server-side binding + position: 2 + "*grid/data-binding/client-side-binding": + title: Client-side Binding + position: 1 + "*grid/data-binding": + title: Data Binding + position: 6 + "*grid/designer": + title: Designer + position: 5 + "*grid/create-radgrid": + title: Create RadGrid + position: 4 + "*grid/structure": + title: Structure + position: 3 + "*gauge/gauge-types": + title: Gauge Types + position: 3 + "*gantt/server-side-programming/objects": + title: Objects + position: 1 + "*gantt/views": + title: Views + position: 15 + "*gantt/import": + title: Import + position: 8 + "*gantt/resources/data-binding": + title: Data Binding + position: 1 + "*gantt/resources": + title: Resources + position: 7 + "*gantt/functionality/import": + title: Import + position: 4 + "*gantt/data-binding/providers": + title: Providers + position: 3 + "*gantt/data-binding/client-side-binding": + title: Client-side Binding + position: 2 + "*gantt/data-binding/server-side-binding/programmatic-binding-": + title: "Programmatic Binding " + position: 1 + "*gantt/data-binding/server-side-binding": + title: Server-side Binding + position: 1 + "*gantt/data-binding": + title: Data Binding + position: 4 + "*gantt/structure": + title: Structure + position: 3 + "*filter/field-editors": + title: Field Editors + position: 4 + "*filter/filter-expressions": + title: Filter Expressions + position: 3 + "*editor/mobile-support/phone-layout/troubleshooting": + title: Troubleshooting + position: 10 + "*editor/mobile-support/phone-layout": + title: Phone Layout + position: 10 + "*editor/performance": + title: Performance + position: 12 + "*editor/client-side-programming/methods/selection": + title: Selection + position: 20 + "*editor/client-side-programming/methods": + title: Methods + position: 14 + "*editor/accessibility-and-internationalization/localization": + title: Localization + position: 3 + "*editor/accessibility-and-internationalization/keyboard-support": + title: Keyboard Support + position: 2 + "*editor/accessibility-and-internationalization/creating-accessible-content": + title: Creating Accessible Content + position: 1 + "*editor/accessibility-and-internationalization/standards-compliance": + title: Standards Compliance + position: 0 + "*editor/managing-content/pasting-content": + title: Pasting Content + position: 2 + "*editor/managing-content/content-area-appearance": + title: Content Area Appearance + position: 1 + "*editor/managing-content/getting-and-setting-content": + title: Getting and Setting Content + position: 0 + "*editor/managing-content": + title: Managing Content + position: 5 + "*editor/functionality/import-and-export": + title: Import and Export + position: 7 + "*editor/functionality/track-changes-and-comments": + title: Track Changes and Comments + position: 6 + "*editor/functionality/editor-views-and-modes": + title: Editor Views and Modes + position: 5 + "*editor/functionality/context-menus": + title: Context Menus + position: 4 + "*editor/functionality/modules": + title: Modules + position: 3 + "*editor/functionality/spellchecker": + title: Spellchecker + position: 2 + "*editor/functionality/dialogs/examples": + title: Examples + position: 9 + "*editor/functionality/dialogs/file-browser-dialogs": + title: File Browser Dialogs + position: 1 + "*editor/functionality/dialogs": + title: Dialogs + position: 1 + "*editor/functionality/toolbars/dropdowns/examples": + title: Examples + position: 16 + "*editor/functionality/toolbars/dropdowns": + title: DropDowns + position: 5 + "*editor/functionality/toolbars/buttons/examples": + title: Examples + position: 4 + "*editor/functionality/toolbars/buttons": + title: Buttons + position: 4 + "*editor/functionality/toolbars": + title: Toolbars + position: 0 + "*dropdowntree/templates": + title: Templates + position: 6 + "*dropdowntree/data-binding": + title: Data Binding + position: 5 + "*dropdownlist/client-side-programming/objects": + title: Objects + position: 3 + "*dropdownlist/templates": + title: Templates + position: 9 + "*dropdownlist/databinding/client-side-binding": + title: Client-Side Binding + position: 2 + "*dropdownlist/databinding/server-side-binding-": + title: "Server-side Binding " + position: 1 + "*dropdownlist/databinding": + title: DataBinding + position: 6 + "*dock/commands": + title: Commands + position: 5 + "*dock/structure/dock-layout": + title: Dock Layout + position: 3 + "*dock/structure/dock-zones": + title: Dock Zones + position: 2 + "*dock/structure/dock": + title: Dock + position: 1 + "*dock/structure": + title: Structure + position: 4 + "*diagram/import-and-export": + title: Import and Export + position: 6 + "*diagram/data-binding/server-side": + title: Server-side + position: 0 + "*diagram/data-binding": + title: Data Binding + position: 4 + "*diagram/structure/layout": + title: Layout + position: 4 + "*diagram/structure": + title: Structure + position: 3 + "*datetimepicker/performance": + title: Performance + position: 14 + "*datetimepicker/templates": + title: Templates + position: 8 + "*datepicker/performance": + title: Performance + position: 14 + "*dateinput/how-to": + title: How to + position: 10 + "*dateinput/client-side-programming": + title: Client-Side Programming + position: 10 + "*dateinput/server-side-programming": + title: Server-Side Programming + position: 9 + "*dateinput/accessibility-and-internationalization": + title: Accessibility and Internationalization + position: 8 + "*dateinput/appearance-and-styling ": + title: Appearance and Styling + position: 7 + "*dateinput/mobile-support/": + title: Mobile Support + position: 6 + "*dateinput/features": + title: Features + position: 5 + "*dateinput/design-time": + title: Design Time + position: 4 + "*datapager/defining-structure": + title: Defining Structure + position: 4 + "*datapager/mobile-support/mobile-rendering": + title: Mobile Rendering + position: 1 + "*datapager/seo-paging": + title: SEO paging + position: 3 + "*datapager/elements-and-templates": + title: Elements and Templates + position: 2 + "*dataform/data-editing": + title: Data Editing + position: 6 + "*dataform/data-binding": + title: Data Binding + position: 3 + "*combobox/client-side-programming/objects": + title: Objects + position: 4 + "*combobox/load-on-demand": + title: Load On Demand + position: 12 + "*combobox/radcombobox-items": + title: RadComboBox Items + position: 11 + "*combobox/data-binding": + title: Data Binding + position: 10 + "*combobox/templates": + title: Templates + position: 9 + "*cloudupload/custom-cloud-storage-providers": + title: Custom Cloud Storage Providers + position: 4 + "*cloudupload/cloud-storage-providers": + title: Cloud Storage Providers + position: 3 + "*clientdatasource/client-side-programming/client-side-api/methods": + title: Methods + position: 1 + "*clientdatasource/client-side-programming/client-side-api/properties": + title: Properties + position: 0 + "*clientdatasource/client-side-programming/client-side-api": + title: Client-side API + position: 3 + "*chat/client-side-programming/objects": + title: Objects + position: 26 + "*chart/client-side": + title: Client-Side + position: 13 + "*chart/standards-compliance": + title: Standards Compliance + position: 12 + "*chart/advanced-topics": + title: Advanced Topics + position: 10 + "*chart/styling-radcharts": + title: Styling RadCharts + position: 9 + "*chart/building-radcharts": + title: Building RadCharts + position: 8 + "*chart/understanding-radchart-ui": + title: Understanding RadChart UI + position: 7 + "*chart/understanding-radchart-elements": + title: Understanding RadChart Elements + position: 6 + "*chart/understanding-radchart-types": + title: Understanding RadChart Types + position: 5 + "*chart/features": + title: Features + position: 4 + "*calendar/templates": + title: Templates + position: 8 + "*button/button-types/icons": + title: Icons + position: 5 + "*button/button-types": + title: Button Types + position: 4 + "*autocompletebox/working-with-entries": + title: Working with Entries + position: 6 + "*autocompletebox/data-binding": + title: Data Binding + position: 5 + "*autocompletebox/templates": + title: Templates + position: 4 + "*autocompletebox/client-side-programming/objects": + title: Objects + position: 4 + controls/*/troubleshooting: + title: Troubleshooting + position: 60 + controls/*/application-scenarios: + title: Application Scenarios + position: 56 + controls/*/how-to: + title: How To + position: 55 + controls/*/client-side-programming/events: + title: Events + position: 25 + controls/*/client-side-programming/methods: + title: Methods + position: 20 + controls/*/client-side-programming/properties: + title: Properties + position: 19 + controls/*/client-side-programming: + title: Client-side Programming + position: 50 + controls/*/server-side-programming/events: + title: Events + position: 25 + controls/*/server-side-programming/methods: + title: Methods + position: 20 + controls/*/server-side-programming: + title: Server-side Programming + position: 45 + controls/*/accessibility-and-internationalization: + title: Accessibility and Internationalization + position: 40 + controls/*/appearance-and-styling: + title: Appearance and Styling + position: 35 + controls/*/mobile-support: + title: Mobile Support + position: 30 + controls/*/functionality: + title: Functionality + position: 12 + controls/*/design-time: + title: Design Time + position: 4 + controls/*/getting-started: + title: Getting Started + position: 3 + controls/*/changes-and-backward-compatibility: + title: Changes and Backwards Compatibility + position: 2 + controls/*/changes-and-backwards-compatibility: + title: Changes and Backwards Compatibility + position: 2 + controls/*/introduction: + title: introduction + position: 1 + controls/*/overview: + title: Overview + position: 1 + controls/xmlhttppanel: + title: XmlHttpPanel + position: 1 + controls/wizard: + title: Wizard + position: 1 + controls/window: + title: Window + position: 1 + controls/upload: + title: Upload (Obsolete) + position: 1 + controls/treeview: + title: TreeView + position: 1 + controls/treemap: + title: TreeMap + position: 1 + controls/treelist: + title: TreeList + position: 1 + controls/tooltip: + title: ToolTip + position: 1 + controls/toolbar: + title: ToolBar + position: 1 + controls/togglebutton: + title: ToggleButton + position: 1 + controls/timepicker: + title: TimePicker + position: 1 + controls/tilelist: + title: TileList + position: 1 + controls/timeline: + title: Timeline + position: 1 + controls/textbox: + title: Textbox + position: 1 + controls/tagcloud: + title: Tag Cloud + position: 1 + controls/tabstrip: + title: Tab Strip + position: 1 + controls/switch: + title: Switch + position: 1 + controls/stylesheetmanager: + title: StyleSheet Manager + position: 1 + controls/stepper: + title: Stepper + position: 1 + controls/spreadsheet: + title: Spreadsheet + position: 1 + controls/splitter: + title: Splitter + position: 1 + controls/splitbutton: + title: SplitButton + position: 1 + controls/spell: + title: Spell + position: 1 + controls/socialshare: + title: Social Share + position: 1 + controls/slider: + title: Slider + position: 1 + controls/skinmanager: + title: SkinManager + position: 1 + controls/sitemap: + title: Sitemap + position: 1 + controls/signature: + title: Signature + position: 1 + controls/searchbox: + title: SearchBox + position: 1 + controls/scriptmanager: + title: Script Manager + position: 1 + controls/scheduler: + title: Scheduler + position: 1 + controls/checkboxlist: + title: CheckBoxList + position: 1 + controls/radiobuttonlist: + title: RadioButtonList + position: 1 + controls/rotator: + title: Rotator + position: 1 + controls/ribbonbar: + title: RibbonBar + position: 1 + controls/rating: + title: Rating + position: 1 + controls/pushbutton: + title: PushButton + position: 1 + controls/progressbar: + title: Progress Bar + position: 1 + controls/progressarea: + title: Progress Area + position: 1 + controls/pivotgrid: + title: Pivot Grid + position: 1 + controls/persistenceframework: + title: Persistence Framework + position: 1 + controls/pdfviewer: + title: PdfViewer + position: 1 + controls/panelbar: + title: PanelBar + position: 1 + controls/pagelayout: + title: Page Layout + position: 1 + controls/orgchart: + title: Org Chart + position: 1 + controls/odatadatasource: + title: OData DataSource + position: 1 + controls/numerictextbox: + title: Numeric Textbox + position: 1 + controls/notification: + title: Notification + position: 1 + controls/navigation: + title: Navigation + position: 1 + controls/multiselect: + title: MultiSelect + position: 1 + controls/multicolumncombobox: + title: MultiColumn ComboBox + position: 1 + controls/monthyearpicker: + title: MonthYearPicker + position: 1 + controls/menu: + title: Menu + position: 1 + controls/mediaplayer: + title: Media Player + position: 1 + controls/maskedtextbox: + title: Masked Textbox + position: 1 + controls/map: + title: Map + position: 1 + controls/listview: + title: ListView + position: 1 + controls/listbox: + title: ListBox + position: 1 + controls/linkbutton: + title: LinkButton + position: 1 + controls/lightbox: + title: LightBox + position: 1 + controls/label: + title: Label + position: 1 + controls/input: + title: Input + position: 1 + controls/imagegallery: + title: Image Gallery + position: 1 + controls/imagebutton: + title: ImageButton + position: 1 + controls/imageeditor: + title: Image Editor + position: 1 + controls/inputmanager: + title: Input Manager + position: 1 + controls/htmlchart: + title: Chart (HTML5) + position: 1 + controls/grid: + title: Grid + position: 1 + controls/gauge: + title: Gauge + position: 1 + controls/gantt: + title: Gantt + position: 1 + controls/formdecorator: + title: Form Decorator + position: 1 + controls/floatingactionbutton: + title: FloatingActionButton + position: 1 + controls/filter: + title: Filter + position: 1 + controls/fileexplorer: + title: File Explorer + position: 1 + controls/editor: + title: Editor + position: 1 + controls/dropdowntree: + title: DropDownTree + position: 1 + controls/dropdownlist: + title: DropDownList + position: 1 + controls/drawer: + title: Drawer + position: 1 + controls/dragdropmanager/client-side-programming/dragdropmanager: + title: DragDropManager + position: 4 + controls/dragdropmanager/client-side-programming/droptargetarea: + title: DropTargetArea + position: 3 + controls/dragdropmanager/client-side-programming/droptarget: + title: DropTarget + position: 2 + controls/dragdropmanager/client-side-programming/draggable: + title: Draggabe + position: 1 + controls/dragdropmanager: + title: DragDropManager + position: 1 + controls/dock: + title: Dock + position: 1 + controls/diagram: + title: Diagram + position: 1 + controls/datetimepicker: + title: DateTimePicker + position: 1 + controls/daterangepicker: + title: DateRangePicker + position: 1 + controls/datepicker: + title: Date Picker + position: 1 + controls/dateinput: + title: Date Input + position: 1 + controls/datapager: + title: Data Pager + position: 1 + controls/dataform: + title: Data Form + position: 1 + controls/combobox: + title: ComboBox + position: 1 + controls/colorpicker: + title: Color Picker + position: 1 + controls/cloudupload: + title: Cloud Upload + position: 1 + controls/clientexportmanager: + title: Client Export Manager + position: 1 + controls/clientdatasource: + title: ClientDataSource + position: 1 + controls/checkbox: + title: CheckBox + position: 1 + controls/chiplist: + title: ChipList + position: 1 + controls/chip: + title: Chip + position: 1 + controls/chat: + title: Chat + position: 1 + controls/chart: + title: Chart (Obsolete) + position: 1 + controls/card: + title: Card + position: 1 + controls/captcha: + title: Captcha + position: 1 + controls/calendar: + title: Calendar + position: 1 + controls/breadcrumb: + title: Breadcrumb + position: 1 + controls/button: + title: Button + position: 1 + controls/binaryimage: + title: BinaryImage + position: 1 + controls/barcode: + title: Barcode + position: 1 + controls/avatar: + title: Avatar + position: 1 + controls/autocompletebox: + title: AutoCompleteBox + position: 1 + controls/asyncupload: + title: Async Upload + position: 1 + controls/ajaxloadingpanel: + title: AjaxLoadingPanel + position: 1 + controls/ajaxmanager/server-side-programming: + title: Server-Side API + position: 80 + controls/ajaxmanager/client-side-programming: + title: Client-Side API + position: 70 + controls/ajaxmanager: + title: AjaxManager + position: 1 + controls/ajaxpanel: + title: AjaxPanel + position: 1 + api/server: + title: Server-side + position: 2 + api/client/enums: + title: Enums + api/client/args: + title: Event Arguments + api/client: + title: Client-side + position: 1 + api: + title: API Reference + position: 30 + upgrade-compatibility/upgrading-instructions: + title: Upgrading + position: 10 + integration/visual-studio/visual-studio-extensions: + title: Visual Studio Extensions + integration/visual-studio/typescript-definitions: + title: TypeScript Definitions + integration/visual-studio: + title: Visual Studio + integration/telerik-products/document-processing: + title: Document Processing Libraries + integration/telerik-products/testing-with-test-studio: + title: Automated Testing with Test Studio + integration/telerik-products: + title: Telerik Products + integration/sharepoint/online: + title: SharePoint Online (Office 365) + position: 4 + integration/sharepoint/2016: + title: SharePoint 2016 + position: 1 + integration/sharepoint/2013/radeditor-web-part/installation-and-deployment: + title: Installation and Deployment + position: 2 + integration/sharepoint/2013/radeditor-web-part: + title: Editor Web Part + position: 1 + integration/sharepoint/2013/installation-and-deployment: + title: Installation and Deployment + position: 0 + integration/sharepoint/2013: + title: SharePoint 2013 + position: 2 + integration/sharepoint/2010/radscheduler-web-part: + title: Scheduler Web Part + position: 4 + integration/sharepoint/2010/radlistview-web-part: + title: ListView Web Part + position: 3 + integration/sharepoint/2010/radgrid-web-part: + title: Grid Web Part + position: 2 + integration/sharepoint/2010/radeditor-web-part/customization: + title: Customization + position: 7 + integration/sharepoint/2010/radeditor-web-part/dialogs: + title: Dialogs + position: 6 + integration/sharepoint/2010/radeditor-web-part/dropdowns: + title: DropDowns + position: 5 + integration/sharepoint/2010/radeditor-web-part/configuration: + title: Configuration + position: 4 + integration/sharepoint/2010/radeditor-web-part/migration-and-upgrade: + title: Migration and Upgrade + position: 3 + integration/sharepoint/2010/radeditor-web-part/installation-and-deployment: + title: Installation and Deployment + position: 2 + integration/sharepoint/2010/radeditor-web-part: + title: Editor Web Part + position: 1 + integration/sharepoint/2010/installation-and-deployment: + title: Installation and Deployment + position: 0 + integration/sharepoint/troubleshooting: + title: Troubleshooting + position: 5 + integration/sharepoint/2010: + title: SharePoint 2010 + position: 3 + integration/sharepoint: + title: Sharepoint + integration/jquery: + title: jQuery + styling/theme-builder: + title: ThemeBuilder + position: 30 + styling/visual-stylebuilder: + title: Visual Stylebuilder + position: 20 + styling/controlling-visual-appearance: + title: Controlling the Appearance + position: 10 + getting-started/performance: + title: Performance + position: 30 + getting-started/prerequisites: + title: Prerequisites + position: 9 + getting-started/work-with-controls: + title: Working with the Controls + position: 20 + getting-started/installation: + title: Download & Installation + position: 10 + knowledge-base: + title: Knowledge Base + position: 30 + res_type: kb + relativeUrl: /knowledge-base + hideChildren: true + upgrade-compatibility: + title: Upgrade & Compatibility + position: 10 + accessibility: + title: Accessibility + position: 9 + mobile-support: + title: Mobile Support + position: 8 + integration: + title: Integration + position: 7 + shared-utilities: + title: Shared Utilities + position: 6 + deployment: + title: Deployment + position: 5 + styling: + title: Styles & Appearance + position: 4 + controls: + title: Controls + position: 3 + getting-started: + title: Getting Started + position: 2 + api/*: + res_type: api + +redirects: +- + from: "^/?$" + to: "/introduction" + type: Permanent +- + from: "^/copyright.*$" + to: "https://www.progress.com/legal/documentation-copyright" + type: Permanent +- + from: "^/gdpr.*$" + to: "https://www.progress.com/legal/privacy-policy" + type: Permanent +- + from: "^/installation/upgrading-instructions/(.*)$" + to: "/upgrade-compatibility/upgrading-instructions/$1" + type: Permanent +- + from: "^/installation/(.*)$" + to: "/getting-started/installation/$1" + type: Permanent +- + from: "^/general-information/using-jquery/(.*)$" + to: "/integration/jquery/$1" + type: Permanent +- + from: "^/mvc(/overview)?(/.*)?$" + to: "/integration/mvc$2" + type: Permanent +- + from: "^/sharepoint/(.*)$" + to: "/integration/sharepoint/$1" + type: Permanent +- + from: "^/integration-with-other-telerik-products/(.*)$" + to: "/integration/telerik-products/$1" + type: Permanent +- + from: "^/general-information/integration-with-visual-studio/(.*)$" + to: "/integration/visual-studio/$1" + type: Permanent +- + from: "^/general-information/performance/(.*)$" + to: "/getting-started/performance/$1" + type: Permanent +- + from: "^/visual-stylebuilder/(.*)$" + to: "/styling/visual-stylebuilder/$1" + type: Permanent +- + from: "^/theme-builder/(.*)$" + to: "/styling/theme-builder/$1" + type: Permanent +- + from: "^/general-information/controlling-visual-appearance/(.*)$" + to: "/styling/controlling-visual-appearance/$1" + type: Permanent +- + from: "^/controls/ajax/radajaxloadingpanel/(.*)$" + to: "/controls/ajaxloadingpanel/$1" + type: Permanent +- + from: "^/controls/ajax/radajaxpanel/(.*)$" + to: "/controls/ajaxpanel/$1" + type: Permanent + +- + from: "^/controls/ajax/radajaxmanager/(.*)$" + to: "/controls/ajaxmanager/$1" + type: Permanent + +- + from: "^/controls/ajax/(.*)$" + to: "/controls/ajaxmanager/$1" + type: Permanent + +- + from: "^/controls/input/radinputmanager/(.*)$" + to: "/controls/inputmanager/$1" + type: Permanent + +- + from: "^/controls/input/radtextbox/overview$" + to: "/controls/textbox/overview" + type: Permanent + +- + from: "^/controls/input/radtextbox/(.*)$" + to: "/controls/textbox/features/$1" + type: Permanent + +- + from: "^/controls/input/(.*)$" + to: "/controls/textbox/$1" + type: Permanent + +- + from: "^/controls/maksedtextbox/(.*)$" + to: "/controls/maskedtextbox/$1" + type: Permanent + +- + from: "(?<=/)pdfprocessing/(.*)" + to: "https://docs.telerik.com/devtools/document-processing/libraries/rad$0" + type: Permanent +- + from: "(?<=/)wordsprocessing/(.*)" + to: "https://docs.telerik.com/devtools/document-processing/libraries/rad$0" + type: Permanent +- + from: "(?<=/)spreadprocessing/(.*)" + to: "https://docs.telerik.com/devtools/document-processing/libraries/rad$0" + type: Permanent +- + from: "(?<=/)spreadstreamprocessing/(.*)" + to: "https://docs.telerik.com/devtools/document-processing/libraries/rad$0" + type: Permanent +- + from: "(?<=/)ziplibrary/(.*)" + to: "https://docs.telerik.com/devtools/document-processing/libraries/rad$0" + type: Permanent diff --git a/getting-started/work-with-controls/adding-the-telerik-controls-to-your-project.md b/getting-started/work-with-controls/adding-the-telerik-controls-to-your-project.md index ed0ded3157..58814e3b3c 100644 --- a/getting-started/work-with-controls/adding-the-telerik-controls-to-your-project.md +++ b/getting-started/work-with-controls/adding-the-telerik-controls-to-your-project.md @@ -3,9 +3,8 @@ title: Adding the Controls to Your Project page_title: Adding the Controls to Your Project description: "Add Telerik UI for ASP.NET AJAX controls to an existing Web Forms project." slug: getting-started/adding-the-telerik-controls-to-your-project -previous_url: getting-started/adding-the-telerik-controls-to-your-project +previous_url: getting-started/adding-the-telerik-controls-to-your-project, general-information/adding-the-telerik-controls-to-your-project tags: adding, the, telerik, controls, to, your, web, forms, project -previous_url: general-information/adding-the-telerik-controls-to-your-project published: True position: 1 --- @@ -38,7 +37,7 @@ Before adding a control to your project, verify that the server, development mac - If the page is a content page or a user control, you can add the ScriptManager to the master or main page. For more information, refer to the Microsoft dedicated article. + If the page is a content page or a user control, you can add the ScriptManager to the master or main page. For more information, refer to the Microsoft dedicated article. Alternatively, you can use the [ScriptManager]({% slug scriptmanager/overview %}), which extends the standard ScriptManager control and adds more features. diff --git a/images/avatar-ninja.svg b/images/avatar-ninja.svg new file mode 100644 index 0000000000..d98c1b207f --- /dev/null +++ b/images/avatar-ninja.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/images/ninja-no-results.svg b/images/ninja-no-results.svg new file mode 100644 index 0000000000..5d84ade55a --- /dev/null +++ b/images/ninja-no-results.svg @@ -0,0 +1,47 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/images/pdf-cover.png b/images/pdf-cover.png new file mode 100644 index 0000000000..ce9967ef4e Binary files /dev/null and b/images/pdf-cover.png differ diff --git a/introduction.md b/introduction.md index 7aa37fb616..ba33e519e8 100644 --- a/introduction.md +++ b/introduction.md @@ -208,6 +208,162 @@ The following table lists all available Telerik UI for ASP.NET AJAX components. * [XmlHttpPanel]({%slug xmlhttppanel/overview%}) --> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ## Support Options For any issues you might come across while working with Telerik UI for ASP.NET AJAX, use any of the following available support channels. Note that sharing quality feedback and ideas will not only benefit the community and improve the products, but may also win you [Telerik points](https://www.telerik.com/community/telerik-points). diff --git a/knowledge-base/asyncupload-insecure-direct-object-reference.md b/knowledge-base/asyncupload-insecure-direct-object-reference.md index cb65503ee1..7cdfd1c492 100644 --- a/knowledge-base/asyncupload-insecure-direct-object-reference.md +++ b/knowledge-base/asyncupload-insecure-direct-object-reference.md @@ -101,7 +101,7 @@ We would like to thank Paul Taylor / Foregenix Ltd and Markus Wulftange of Code [CVE-2017-11357](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11357) -# See Also +## See Also - [Security]({%slug general-information/security%}) diff --git a/knowledge-base/asyncupload-red-dot-shown-file-not-uploaded-troubleshooting.md b/knowledge-base/asyncupload-red-dot-shown-file-not-uploaded-troubleshooting.md index 069f67d4db..0f7cd9155c 100644 --- a/knowledge-base/asyncupload-red-dot-shown-file-not-uploaded-troubleshooting.md +++ b/knowledge-base/asyncupload-red-dot-shown-file-not-uploaded-troubleshooting.md @@ -7,16 +7,16 @@ slug: asyncupload-red-dot-shown-file-not-uploaded-troubleshooting tags: red dot, file not uploaded, troubleshooting, RadAsyncUpload, ASP.NET AJAX res_type: kb --- -# Environment +## Environment | Property | Value | | --- | --- | | Product | RadAsyncUpload for ASP.NET AJAX | | Version | all | -# Description +## Description I am experiencing an issue where a red dot is shown next to every file I attempt to upload, and the files are not being uploaded successfully. -# Solution +## Solution To resolve this issue, follow these steps: - Check if you have write permission to your temporary folder. If you are hosting your application in IIS, make sure you have assigned additional permissions to the temporary folder. By default, the temporary upload folder is located at `~/App_Data/RadUploadTemp`. Ensure that the folder has full read and write permissions. - Verify that the `Telerik.Web.UI.WebResource.axd` handler is registered in the `web.config` file. Open the `web.config` file and add the following code snippet within the `` section: diff --git a/knowledge-base/autocompletebox-allow-multiselection.md b/knowledge-base/autocompletebox-allow-multiselection.md index 3feb07a3fc..80271b99fd 100644 --- a/knowledge-base/autocompletebox-allow-multiselection.md +++ b/knowledge-base/autocompletebox-allow-multiselection.md @@ -1,57 +1,57 @@ ---- -title: AutoCompleteBox to remain with open dropdown to allow multiselection -description: AutoCompleteBox to remain with open dropdown to allow multiselection. Check it now! -type: how-to -page_title: AutoCompleteBox to remain with open dropdown to allow multiselection -slug: autocompletebox-allow-multiselection -res_type: kb ---- - - -### HOW TO - -Configure the AutoCompleteBox imitate the behavior of the [Kendo UI MultiSelect](https://demos.telerik.com/kendo-ui/multiselect/index) widget by allowing the selection of multiple items without closing the dropdown on item click. - -![AutoCompleteBox-MultiSelection](images\autocompletebox-multiselection.gif) - -### SOLUTION - -Remove the default click handler of the items container of the AutoCompleteBox' dropdown: - -````ASP.NET - - - -```` - -````C# -protected void Page_Init(object sender, EventArgs e) -{ - RadAutoCompleteBox1.DataSource = new string[] { "Item 1", "Item 2", "Item 3" }; - RadAutoCompleteBox1.DataBind(); -} -```` -````VB -Protected Sub Page_Init(ByVal sender As Object, ByVal e As EventArgs) - RadAutoCompleteBox1.DataSource = New String() {"Item 1", "Item 2", "Item 3"} - RadAutoCompleteBox1.DataBind() -End Sub -```` - - +--- +title: AutoCompleteBox to remain with open dropdown to allow multiselection +description: AutoCompleteBox to remain with open dropdown to allow multiselection. Check it now! +type: how-to +page_title: AutoCompleteBox to remain with open dropdown to allow multiselection +slug: autocompletebox-allow-multiselection +res_type: kb +--- + + +### HOW TO + +Configure the AutoCompleteBox imitate the behavior of the [Kendo UI MultiSelect](https://demos.telerik.com/kendo-ui/multiselect/index) widget by allowing the selection of multiple items without closing the dropdown on item click. + +![AutoCompleteBox-MultiSelection](images/autocompletebox-multiselection.gif) + +### SOLUTION + +Remove the default click handler of the items container of the AutoCompleteBox' dropdown: + +````ASP.NET + + + +```` + +````C# +protected void Page_Init(object sender, EventArgs e) +{ + RadAutoCompleteBox1.DataSource = new string[] { "Item 1", "Item 2", "Item 3" }; + RadAutoCompleteBox1.DataBind(); +} +```` +````VB +Protected Sub Page_Init(ByVal sender As Object, ByVal e As EventArgs) + RadAutoCompleteBox1.DataSource = New String() {"Item 1", "Item 2", "Item 3"} + RadAutoCompleteBox1.DataBind() +End Sub +```` + + diff --git a/knowledge-base/calendar-making-non-special-days-unselectable.md b/knowledge-base/calendar-making-non-special-days-unselectable.md index b0315a5033..484093358c 100644 --- a/knowledge-base/calendar-making-non-special-days-unselectable.md +++ b/knowledge-base/calendar-making-non-special-days-unselectable.md @@ -7,7 +7,7 @@ slug: calendar-making-non-special-days-unselectable tags: radcalendar, asp.net ajax, unselectable days, special days res_type: kb --- -# Environment +## Environment | Product | Version | |---------|---------| | RadCalendar for ASP.NET AJAX | all | diff --git a/knowledge-base/common-error-stylesheetmanager-requires-httphandler-registration.md b/knowledge-base/common-error-stylesheetmanager-requires-httphandler-registration.md index 94510f87e1..8f56a179cb 100644 --- a/knowledge-base/common-error-stylesheetmanager-requires-httphandler-registration.md +++ b/knowledge-base/common-error-stylesheetmanager-requires-httphandler-registration.md @@ -1,8 +1,8 @@ --- -title: Error: '~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadStyleSheetManager requires a HttpHandler registration in web.config. -description: Error: '~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadStyleSheetManager requires a HttpHandler registration in web.config. +title: "Error: '~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadStyleSheetManager requires a HttpHandler registration in web.config." +description: "Error: '~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadStyleSheetManager requires a HttpHandler registration in web.config." type: troubleshooting -page_title: Error: '~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadStyleSheetManager requires a HttpHandler registration in web.config. +page_title: "Error: '~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadStyleSheetManager requires a HttpHandler registration in web.config." slug: common-error-stylesheetmanager-requires-httphandler-registration position: tags: diff --git a/knowledge-base/common-http-error-500-19-this-configuration-section-cannot-be-used-at-this-path.md b/knowledge-base/common-http-error-500-19-this-configuration-section-cannot-be-used-at-this-path.md index 3ca1fa9140..d5f2e9b25b 100644 --- a/knowledge-base/common-http-error-500-19-this-configuration-section-cannot-be-used-at-this-path.md +++ b/knowledge-base/common-http-error-500-19-this-configuration-section-cannot-be-used-at-this-path.md @@ -1,5 +1,5 @@ --- -title: HTTP Error 500.19 Config error: This configuration section cannot be used at this path +title: "HTTP Error 500.19 Config error: This configuration section cannot be used at this path" description: Config Error This configuration section cannot be used at this path. Check out how to fix it. type: troubleshooting page_title: HTTP Error 500.19 Config error This configuration section cannot be used at this path diff --git a/knowledge-base/common-incorrect-positioning-of-controls.md b/knowledge-base/common-incorrect-positioning-of-controls.md index 8418b2c437..504eb437da 100644 --- a/knowledge-base/common-incorrect-positioning-of-controls.md +++ b/knowledge-base/common-incorrect-positioning-of-controls.md @@ -54,7 +54,7 @@ All problems demonstrated above are due to special positioning of the body, form - OR, move the special positioning from the <form|body|parent element> to another element that is not a parent of the AJAX control. For example put all the content/layout in a <div> inside the form: - ````ASPX +````ASPX @@ -82,7 +82,7 @@ All problems demonstrated above are due to special positioning of the body, form - ```` +```` **Tip**: You can use the browser dev toolbar to inspect the rendered HTML in order to see where the Telerik control renders, what its parents are and what CSS is applied to them. diff --git a/knowledge-base/common-resolve-cs0234-error-telerik-quickstart-namespace.md b/knowledge-base/common-resolve-cs0234-error-telerik-quickstart-namespace.md index b07754e7bc..c9f9b0921e 100644 --- a/knowledge-base/common-resolve-cs0234-error-telerik-quickstart-namespace.md +++ b/knowledge-base/common-resolve-cs0234-error-telerik-quickstart-namespace.md @@ -7,15 +7,15 @@ slug: common-resolve-cs0234-error-telerik-quickstart-namespace tags: telerik, quickstart, namespace, error, CS0234 res_type: kb --- -# Environment +## Environment | Product | Version | |---------|---------| | Telerik UI for ASP.NET AJAX | all | -# Description +## Description I am encountering the "CS0234: The type or namespace name 'QuickStart' does not exist in the namespace 'Telerik' (are you missing an assembly reference?)" error when using the Telerik.QuickStart namespace. I have tried to find the QuickStart files or DLL in my Telerik package but have been unsuccessful. -# Solution +## Solution The Telerik.QuickStart namespace is part of the demo website and is used only for the purposes of the demos. To resolve this error, follow these steps: @@ -29,10 +29,10 @@ To resolve this error, follow these steps: Alternatively, the [Isolate this demo as a stand-alone application page](http://demos.telerik.com/aspnet-ajax/Common/QSFInstructions/Instructions.html) shows how to remove it from the demos. This page is available as a link on each demo along with a download option with ready-to-use demo files (Download demo code files): -# Notes +## Notes - The QuickStart namespace is only used in the Telerik AJAX demo website and is not required to use your project's Telerik controls. - The QuickStart files provided in the demos are written in C#. If you are using a Visual Basic project, you may need to convert the code to Visual Basic yourself. -# See Also +## See Also - [Isolating Telerik Demos as Stand-alone Applications](http://demos.telerik.com/aspnet-ajax/Common/QSFInstructions/Instructions.html) diff --git a/knowledge-base/common-script-control-not-registered-error-after-upgrade.md b/knowledge-base/common-script-control-not-registered-error-after-upgrade.md index 90761a7f72..3edc5d79ca 100644 --- a/knowledge-base/common-script-control-not-registered-error-after-upgrade.md +++ b/knowledge-base/common-script-control-not-registered-error-after-upgrade.md @@ -8,12 +8,12 @@ tags: script-control, error, upgrade, Telerik UI for ASP.NET AJAX res_type: kb --- -# Description +## Description Users utilizing Telerik UI for ASP.NET AJAX might encounter script control registration errors during development or runtime. These errors are typically presented as "Script control 'TelerikControlID' is not a registered script control. Script controls must be registered using RegisterScriptControl() before calling RegisterScriptDescriptors()." Such issues are prevalent in scenarios where asynchronous patterns, like using Async="true" in the page directive or employing asynchronous task methods in the code-behind, are applied alongside Telerik UI controls. The core of these problems lies in the incompatibility or specific challenges of using the async-await pattern within WebForms that include Telerik UI for ASP.NET AJAX controls. While the async-await pattern is highly beneficial for creating responsive applications by performing non-blocking operations, its integration with certain UI controls requires careful handling to prevent runtime errors and ensure smooth operation. -# Solution +## Solution 1. Remove or disable async operations in the page directive and the code-behind. Specifically, set Async="false" in the page directive (if present) and convert asynchronous task methods back to synchronous methods where Telerik controls are involved. This change addresses the immediate issue by avoiding the async-await pattern that Telerik UI for ASP.NET AJAX controls struggle with. You can find more information [here](https://docs.telerik.com/devtools/aspnet-ajax/knowledge-base/common-errors-when-page-async-is-true-for-the-async-await-pattern). diff --git a/knowledge-base/common-use-material-skin-without-active-internet-connection.md b/knowledge-base/common-use-material-skin-without-active-internet-connection.md index bf6f5f6300..b68965a974 100644 --- a/knowledge-base/common-use-material-skin-without-active-internet-connection.md +++ b/knowledge-base/common-use-material-skin-without-active-internet-connection.md @@ -69,7 +69,7 @@ The second approach is to create a local CDN where you will make the changes to -### Prevent the references to https://fonts.gstatic.com +### Prevent the references to fonts.gstatic.com If the [Content Security Policy is enabled in IIS](https://docs.telerik.com/devtools/aspnet-ajax/general-information/troubleshooting/content-security-policy), you may experience calls to https://fonts.gstatic.com. The presence of the *font-src 'self'* section causes Chrome to evaluate all fonts on the page and this will also trigger requests to the Google cloud for the Roboto font, even if it is not used by the page (i.e., the Material skin is not used). diff --git a/knowledge-base/diagram-change-shape-visual-template-dynamically.md b/knowledge-base/diagram-change-shape-visual-template-dynamically.md index de071b2899..65b1fa2840 100644 --- a/knowledge-base/diagram-change-shape-visual-template-dynamically.md +++ b/knowledge-base/diagram-change-shape-visual-template-dynamically.md @@ -13,7 +13,7 @@ res_type: kb In this sample you can see how to change the shape’s Visual Template dynamically (e.g. on a shape click). You can test the result of the implementation shown below applied to the Kendo Diagram widget here: [http://dojo.telerik.com/UJizAfOr/3](http://dojo.telerik.com/UJizAfOr/3) -![digram-visual-change]([images/digram-visual-change.gif")  +![digram-visual-change](images/digram-visual-change.gif)  ## SOLUTION diff --git a/knowledge-base/display-binary-image-radavatar-aspnet-ajax.md b/knowledge-base/display-binary-image-radavatar-aspnet-ajax.md index af310425e6..1dc1fe5485 100644 --- a/knowledge-base/display-binary-image-radavatar-aspnet-ajax.md +++ b/knowledge-base/display-binary-image-radavatar-aspnet-ajax.md @@ -8,15 +8,15 @@ tags: binary-image, RadAvatar, ASP.NET AJAX res_type: kb --- -# Environment +## Environment | Property | Value | |----------|-------| | Product | RadBinaryImage for ASP.NET AJAX | -# Description +## Description I want to display a binary image from a SQL datasource in the RadAvatar control for ASP.NET AJAX instead of providing a URL for the image. -# Solution +## Solution To display a binary image from a SQL datasource in the RadAvatar control, you need to serve the binary image data through a handler or a similar endpoint that can convert the binary data into a stream that the browser can interpret as an image. Here are the steps to achieve this: 1. Implement a generic handler (ImageHandler.ashx) in your project: diff --git a/knowledge-base/editor-content-not-saved-after-ajax-update-in-ie9-firefox-google-chrome-and-safari.md b/knowledge-base/editor-content-not-saved-after-ajax-update-in-ie9-firefox-google-chrome-and-safari.md index 3ab6fbb650..e0cd05ab27 100644 --- a/knowledge-base/editor-content-not-saved-after-ajax-update-in-ie9-firefox-google-chrome-and-safari.md +++ b/knowledge-base/editor-content-not-saved-after-ajax-update-in-ie9-firefox-google-chrome-and-safari.md @@ -9,7 +9,7 @@ res_type: kb ## Description -In scenarios in which RadEditor and an ** @@ -46,17 +46,17 @@ protected void btnSave_Click(object sender, EventArgs e) Telerik UI for ASP.NET AJAX, such as RadEditor and RadAjax are built on top of MS AJAX and rely on its mechanism to be informed about partial page updates. Unfortunately in the case of ImageButtons and server buttons, by the time the MS AJAX framework "informs" the editor that a partial update is about to occur, the POST data has already been collected and recorded. The editor does not get a chance to set the updated content properly. The problem exists in Firefox, Chrome, Safari and Internet Explorer 9+. -### Solution for controls: +### Solution for <asp:Button> controls: In order to fix the problem you will have to set the "submit" button's property **UseSubmitBehavior="false"**, e.g. ````ASP.NET ```` -OR use instead of . RadAjaxPanel will add the **UseSubmitBehavior="false"** behavior automatically to all push buttons. +OR use `` instead of ``. RadAjaxPanel will add the **UseSubmitBehavior="false"** behavior automatically to all push buttons. -### Solution for controls: +### Solution for <asp:ImageButton> controls: Since the tags with no text but with font-icons or images. +By default, the tools in the Lightweight RenderMode are rendered as `` tags with no text but with font-icons or images. ````ASP.NET ```` -##SOLUTION +## SOLUTION -The problem occurs when the RadEditor container to the page is loaded using AJAX. This is a well known limitation of the MS AJAX that will not parse ```` -4. The *combinePathsInAString* function accepts an array of type [Telerik.Web.UI.FileExplorerItem]({%slug fileexplorer/client-side-programming/overview}) - the selected items, and returns a string that contains all of the items paths: +4. The *combinePathsInAString* function accepts an array of type [Telerik.Web.UI.FileExplorerItem]({%slug fileexplorer/client-side-programming/overview %}) - the selected items, and returns a string that contains all of the items paths: ````ASP.NET diff --git a/knowledge-base/gauge-radgauge-with-display-none-does-not-render-properly.md b/knowledge-base/gauge-radgauge-with-display-none-does-not-render-properly.md index d0418ba28c..fd5a468ad6 100644 --- a/knowledge-base/gauge-radgauge-with-display-none-does-not-render-properly.md +++ b/knowledge-base/gauge-radgauge-with-display-none-does-not-render-properly.md @@ -1,8 +1,8 @@ --- -title: RadGauge with 'display: none' does not render properly -description: RadGauge with 'display: none' does not render properly. Check it now! +title: "RadGauge with 'display: none' does not render properly" +description: "RadGauge with 'display: none' does not render properly. Check it now!" type: how-to -page_title: RadGauge with 'display: none' does not render properly +page_title: "RadGauge with 'display: none' does not render properly" slug: gauge-radgauge-with-display-none-does-not-render-properly res_type: kb --- diff --git a/knowledge-base/grid-clientdatasource-binding-after-filtering-so-no-records-are-present-and-removing-the-filter-there-is-no-pager.md b/knowledge-base/grid-clientdatasource-binding-after-filtering-so-no-records-are-present-and-removing-the-filter-there-is-no-pager.md index 6111482355..994776824f 100644 --- a/knowledge-base/grid-clientdatasource-binding-after-filtering-so-no-records-are-present-and-removing-the-filter-there-is-no-pager.md +++ b/knowledge-base/grid-clientdatasource-binding-after-filtering-so-no-records-are-present-and-removing-the-filter-there-is-no-pager.md @@ -1,8 +1,8 @@ --- -title: RadGrid ClientDataSource binding: after filtering so no records are present and removing the filter there is no pager -description: ClientDataSource binding: after filtering so no records are present and removing the filter there is no pager. Check it now! +title: "RadGrid ClientDataSource binding: after filtering so no records are present and removing the filter there is no pager" +description: "ClientDataSource binding: after filtering so no records are present and removing the filter there is no pager. Check it now!" type: how-to -page_title: RadGrid ClientDataSource binding: after filtering so no records are present and removing the filter there is no pager +page_title: "RadGrid ClientDataSource binding: after filtering so no records are present and removing the filter there is no pager" slug: grid-clientdatasource-binding-after-filtering-so-no-records-are-present-and-removing-the-filter-there-is-no-pager res_type: kb --- diff --git a/knowledge-base/grid-clientdatasource-binding-and-batch-editing-page-is-reset-to-1-after-deleting-a-record.md b/knowledge-base/grid-clientdatasource-binding-and-batch-editing-page-is-reset-to-1-after-deleting-a-record.md index e5dca042ee..c4061f4601 100644 --- a/knowledge-base/grid-clientdatasource-binding-and-batch-editing-page-is-reset-to-1-after-deleting-a-record.md +++ b/knowledge-base/grid-clientdatasource-binding-and-batch-editing-page-is-reset-to-1-after-deleting-a-record.md @@ -1,8 +1,8 @@ --- -title: RadGrid ClientDataSource binding and batch editing: page is reset to 1 after deleting a record -description: RadGrid ClientDataSource binding and batch editing: page is reset to 1 after deleting a record. Check it now! +title: "RadGrid ClientDataSource binding and batch editing: page is reset to 1 after deleting a record" +description: "RadGrid ClientDataSource binding and batch editing: page is reset to 1 after deleting a record. Check it now!" type: how-to -page_title: RadGrid ClientDataSource binding and batch editing: page is reset to 1 after deleting a record +page_title: "RadGrid ClientDataSource binding and batch editing: page is reset to 1 after deleting a record" slug: grid-clientdatasource-binding-and-batch-editing-page-is-reset-to-1-after-deleting-a-record res_type: kb --- diff --git a/knowledge-base/grid-colorpicker-insert-and-update-records.md b/knowledge-base/grid-colorpicker-insert-and-update-records.md index 62950cb548..e087fe7931 100644 --- a/knowledge-base/grid-colorpicker-insert-and-update-records.md +++ b/knowledge-base/grid-colorpicker-insert-and-update-records.md @@ -1,31 +1,31 @@ ---- -title: How to insert and update records in a RadGrid with columns that contain RadColorPicker -description: How to insert and update records in a RadGrid with columns that contain RadColorPicker. Check it now! -type: how-to -page_title: How to insert and update records in a RadGrid with columns that contain RadColorPicker -slug: how-to-insert-and-update-records-in-a-radgrid-with-columns-that-contain-radcolorpicker -res_type: kb ---- - -| Product | RadColorPicker for ASP.NET AJAX | -| --- | --- | -| Version | Current | - - - -## HOW-TO - -This article shows how to bind a **RadGridTemplateColumn **that contains a **RadColorPicker **to a *SqlDataSource*. The code for inserting a new record to -the DataBase and updating an existing record are shown in the attached projects. - - ## DESCRIPTION - -The MSSQL server does not have a type corresponding to the *System.Drawing.Color* type in .NET. The **RadColorPicker** control works with that .NET type, however. - -## SOLUTION - -In the attached sample a column of type *nvarchar* is used to store the value of the color (an example value is: *#66CC99*) in the SQL server. The *FromHtml*and *ToHtml* static methods of the [System.Drawing.ColorTranslator](https://learn.microsoft.com/en-us/dotnet/api/system.drawing.colortranslator?view=net-8.0&redirectedfrom=MSDN) class are used to parse a string to an object of type *System.Drawing.Color* and vice-versa. The zip files below contain the full source code of the implementation in VB.NET and C# including -the database file used in the sample. - - - +--- +title: How to insert and update records in a RadGrid with columns that contain RadColorPicker +description: How to insert and update records in a RadGrid with columns that contain RadColorPicker. Check it now! +type: how-to +page_title: How to insert and update records in a RadGrid with columns that contain RadColorPicker +slug: how-to-insert-and-update-records-in-a-radgrid-with-columns-that-contain-radcolorpicker +res_type: kb +--- + +| Product | RadColorPicker for ASP.NET AJAX | +| --- | --- | +| Version | Current | + + + +## HOW-TO + +This article shows how to bind a **RadGridTemplateColumn **that contains a **RadColorPicker **to a *SqlDataSource*. The code for inserting a new record to +the DataBase and updating an existing record are shown in the attached projects. + + ## DESCRIPTION + +The MSSQL server does not have a type corresponding to the *System.Drawing.Color* type in .NET. The **RadColorPicker** control works with that .NET type, however. + +## SOLUTION + +In the attached sample a column of type *nvarchar* is used to store the value of the color (an example value is: *#66CC99*) in the SQL server. The *FromHtml*and *ToHtml* static methods of the [System.Drawing.ColorTranslator](https://learn.microsoft.com/en-us/dotnet/api/system.drawing.colortranslator?view=net-8.0&redirectedfrom=MSDN) class are used to parse a string to an object of type *System.Drawing.Color* and vice-versa. The zip files below contain the full source code of the implementation in VB.NET and C# including +the database file used in the sample. + + + diff --git a/knowledge-base/grid-drag-and-drop-over-header-item.md b/knowledge-base/grid-drag-and-drop-over-header-item.md index 82ffcd0336..969111cab2 100644 --- a/knowledge-base/grid-drag-and-drop-over-header-item.md +++ b/knowledge-base/grid-drag-and-drop-over-header-item.md @@ -358,7 +358,7 @@ protected class Order #endregion ```` -# See Also +## See Also * [Items Drag-and-drop demo](https://demos.telerik.com/aspnet-ajax/grid/examples/columns-rows/rows/drag-and-drop/defaultcs.aspx) diff --git a/knowledge-base/grid-how-to-bind-radgrid-properly-on-server-side.md b/knowledge-base/grid-how-to-bind-radgrid-properly-on-server-side.md index ae56b6d1da..ff0dabdaf5 100644 --- a/knowledge-base/grid-how-to-bind-radgrid-properly-on-server-side.md +++ b/knowledge-base/grid-how-to-bind-radgrid-properly-on-server-side.md @@ -29,7 +29,7 @@ Performing complex grid operations such as Inserting, Deleting, Updating, Hierar In some scenarios it may be necessary the grid to be refreshed explicitly upon some external action - in such cases please choose to use just the **Rebind()** method, which will refresh the grid content. -# See Also +## See Also * [Declarative DataSource]({%slug grid/data-binding/server-side-binding/declarative-datasource%}) diff --git a/knowledge-base/grid-migration-from-aspnet-classic-to-aspnet-ajax.md b/knowledge-base/grid-migration-from-aspnet-classic-to-aspnet-ajax.md index b1a47f2213..6307c2b91a 100644 --- a/knowledge-base/grid-migration-from-aspnet-classic-to-aspnet-ajax.md +++ b/knowledge-base/grid-migration-from-aspnet-classic-to-aspnet-ajax.md @@ -195,7 +195,7 @@ The HTML rendering and CSS skins of RadGrid for ASP.NET AJAX (code name "Prometh - **PagerLeft\_Skin, PagerRight\_Skin, PagerCenter\_Skin** - applied to the different components of the pager - **sliderPagerLabel\_Skin** - applied when using RadSlider as a pager - **GridGroupFooter\_Vista** - applied to a group footer row -- RadGrid is now capable of using CSS sprites for all its image buttons and skin images. Please refer to the [RadGrid CSS sprites](ms-its:C:\Users\jekov\Desktop\Telerik_UI_For_ASPNET_AJAX.chm::/html/5EB51F09-6EE7-4EAB-BA7A-F837453CD44E.htm) help topic for further information. If you are migrating a "classic" RadGrid skin to "Prometheus", you are not required to create a CSS sprite, but you need to set the **ImagesPath** property instead, in order to specify the location of all RadGrid skin images and image buttons. +- RadGrid is now capable of using CSS sprites for all its image buttons and skin images. Please refer to the RadGrid CSS sprites help topic for further information. If you are migrating a "classic" RadGrid skin to "Prometheus", you are not required to create a CSS sprite, but you need to set the **ImagesPath** property instead, in order to specify the location of all RadGrid skin images and image buttons. **Removed CSS classes from RadGrid for ASP.NET AJAX** diff --git a/knowledge-base/grid-set-default-insert-value-when-adding-new-records-in-grid.md b/knowledge-base/grid-set-default-insert-value-when-adding-new-records-in-grid.md index 20469777b4..315fd2b4d7 100644 --- a/knowledge-base/grid-set-default-insert-value-when-adding-new-records-in-grid.md +++ b/knowledge-base/grid-set-default-insert-value-when-adding-new-records-in-grid.md @@ -35,6 +35,6 @@ The alternative approach for Batch editing is different since this mode is diffe Therefore, with Batch editing you can use the following event handler to achieve this requirement by accessing the generated controls on client-side using jQuery: -[OnBatchEditOpened]({%slug grid/client-side-programming/events/onbatcheditopened%}}) +[OnBatchEditOpened]({%slug grid/client-side-programming/events/onbatcheditopened%}) diff --git a/knowledge-base/how-to-apply-different-skins-to-radchat-control.md b/knowledge-base/how-to-apply-different-skins-to-radchat-control.md index 4075dd9427..80090e5d77 100644 --- a/knowledge-base/how-to-apply-different-skins-to-radchat-control.md +++ b/knowledge-base/how-to-apply-different-skins-to-radchat-control.md @@ -7,15 +7,15 @@ slug: how-to-apply-different-skins-to-radchat-control tags: radchat, skins, customization res_type: kb --- -# Environment +## Environment | Product | RadChat for ASP.NET AJAX | |-----------------|--------------------------| | Version | all | -# Description +## Description I want to apply a different skin to the RadChat control in RadChat for ASP.NET AJAX. However, when I set the `Skin` attribute to "Bootstrap", I encounter the following error message in the console: "Failed to load resource: the server responded with a status of 404 (not found)". How can I apply different skins to the RadChat control successfully? -# Solution +## Solution Currently, the RadChat control only supports the "Default" skin. Therefore, setting the `Skin` attribute to a different skin, such as "Bootstrap", will result in an error. The RadChat control has been designed with a specific look and feel that aligns with its functionality and user experience, and it currently does not include other embedded skins. If you want to customize the appearance of the RadChat control beyond what is provided by the "Default" skin, you can use custom CSS to achieve your desired look. This approach allows you to override the default styles and create a custom appearance that matches your application's theme. diff --git a/knowledge-base/htmlchart-exporting-to-png-and-pdf.md b/knowledge-base/htmlchart-exporting-to-png-and-pdf.md index c068ccc7b2..da1e156a3c 100644 --- a/knowledge-base/htmlchart-exporting-to-png-and-pdf.md +++ b/knowledge-base/htmlchart-exporting-to-png-and-pdf.md @@ -288,8 +288,8 @@ Two simple sites are attached to the thread (one in C# and one in VB) that show A static class is used for the actual creation of the PNG/PDF file and for sending it to the client (HtmlChartExporter). Comments in the code itself provide more detailed explanations over each action. -[Download C# project](files/htmlchart-exporting-to-png-and-pdfC#.zip)
    -[Download VB project](files/htmlchart-exporting-to-png-and-pdfVB.zip.zip) +[Download C# project](files/htmlchart-exporting-to-png-and-pdfC%23.zip)
    +[Download VB project](files/htmlchart-exporting-to-png-and-pdfVB.zip) diff --git a/knowledge-base/imageeditor-how-to-initially-zoom-the-loaded-image-to-best-fit.md b/knowledge-base/imageeditor-how-to-initially-zoom-the-loaded-image-to-best-fit.md index 4fc5ccce25..8f7076d83e 100644 --- a/knowledge-base/imageeditor-how-to-initially-zoom-the-loaded-image-to-best-fit.md +++ b/knowledge-base/imageeditor-how-to-initially-zoom-the-loaded-image-to-best-fit.md @@ -27,7 +27,7 @@ In order to zoom to best fit the loaded image, you can attach a handler to the I ## See Also - - [RadImageEditor's OnClientImageLoad Event]({%slug imageeditor/client-side-programming/events/onclientimageload%}}) + - [RadImageEditor's OnClientImageLoad Event]({%slug imageeditor/client-side-programming/events/onclientimageload%}) - [RadImageEditor's Client-side Programming Overview]({%slug imageeditor/client-side-programming/overview%}) diff --git a/knowledge-base/menu-integrating-radajaxloadingpanel-navigation-site-pages.md b/knowledge-base/menu-integrating-radajaxloadingpanel-navigation-site-pages.md index 6171697d44..df0842f850 100644 --- a/knowledge-base/menu-integrating-radajaxloadingpanel-navigation-site-pages.md +++ b/knowledge-base/menu-integrating-radajaxloadingpanel-navigation-site-pages.md @@ -7,15 +7,15 @@ slug: menu-integrating-radajaxloadingpanel-navigation-site-pages tags: radajax, radmenu, radajaxloadingpanel, site pages res_type: kb --- -# Environment +## Environment | Product | Version | |---------|---------| | RadAjax for ASP.NET AJAX | all | -# Description +## Description A common scenario involves a web application using a Site Master Page with Telerik's RadMenu (mnuMain). The challenge faced is how to show the RadAjaxLoadingPanel while the page is navigating to the selected item's URL. Traditional methods using the NavigateUrl property or the onbeforeunload event have limitations and inconsistencies. -# Solution +## Solution The solution involves a client-side JavaScript approach, enhancing the user interaction by displaying the loading panel before navigating to a new page. The key steps are: 1. Remove the NavigateUrl Property: On the server side, remove the NavigateUrl attribute from the RadMenu items. This prevents the standard navigation process, allowing for custom handling. diff --git a/knowledge-base/pass-more-than-one-argument-ajaxrequest-ajaxmanager.md b/knowledge-base/pass-more-than-one-argument-ajaxrequest-ajaxmanager.md index 3bdc307858..0d0ce64b6f 100644 --- a/knowledge-base/pass-more-than-one-argument-ajaxrequest-ajaxmanager.md +++ b/knowledge-base/pass-more-than-one-argument-ajaxrequest-ajaxmanager.md @@ -35,29 +35,26 @@ To achieve the desired scenario and pass two or more arguments in the functions: 1. Join the arguments on the client. - ````JavaScript - var arg3 = arg1 + "," + arg2; - ajaxManager.ajaxRequest(arg3); - ```` - + ````JavaScript + var arg3 = arg1 + "," + arg2; + ajaxManager.ajaxRequest(arg3); + ```` 1. Split the arguments on the server in the `AjaxManager_AjaxRequest`. - ````C# - private void RadAjaxManager1_AjaxRequest(object sender, AjaxRequestEventArgs e) - { - string argument = (e.Argument); - String[] stringArray = argument.Split(",".ToCharArray()); - } - ```` - ````VB.NET - Protected Sub RadAjaxManager1_AjaxRequest(ByVal sender As Object, ByVal e As AjaxRequestEventArgs) Handles RadAjaxManager1.AjaxRequest - Dim argument As String = e.Argument - Dim stringArray As [String]() = argument.Split(",".ToCharArray()) - End Sub - - - ```` + ````C# + private void RadAjaxManager1_AjaxRequest(object sender, AjaxRequestEventArgs e) + { + string argument = (e.Argument); + String[] stringArray = argument.Split(",".ToCharArray()); + } + ```` + ````VB.NET + Protected Sub RadAjaxManager1_AjaxRequest(ByVal sender As Object, ByVal e As AjaxRequestEventArgs) Handles RadAjaxManager1.AjaxRequest + Dim argument As String = e.Argument + Dim stringArray As [String]() = argument.Split(",".ToCharArray()) + End Sub + ```` ## See Also diff --git a/knowledge-base/pdfviewer-loading-blurry-pdf.md b/knowledge-base/pdfviewer-loading-blurry-pdf.md index 232e157c45..a4cbba63cc 100644 --- a/knowledge-base/pdfviewer-loading-blurry-pdf.md +++ b/knowledge-base/pdfviewer-loading-blurry-pdf.md @@ -7,13 +7,13 @@ slug: pdfviewer-loading-blurry-pdf tags: radpdfviewer, ajax, blurry, load, initial, ASP.NET res_type: kb --- -# Description +## Description When initially loading a PDF into the RadPdfViewer for ASP.NET AJAX, parts of the PDF appear blurred and the line thickness is incorrect. -# Cause +## Cause The initial loading issue with the blurred PDF may be caused by a combination of factors, including the version of the RadPdfViewer control and pdf.js library as well as to the scaling settings applied to the PDF. -# Solution +## Solution To resolve the issue of the blurry initial load of the PDF in RadPdfViewer for ASP.NET AJAX, follow these steps: 1. Upgrade to the latest version of RadPdfViewer diff --git a/knowledge-base/pdfviewer-set-initial-page-zoom.md b/knowledge-base/pdfviewer-set-initial-page-zoom.md index 67d47f6e16..7214d9462e 100644 --- a/knowledge-base/pdfviewer-set-initial-page-zoom.md +++ b/knowledge-base/pdfviewer-set-initial-page-zoom.md @@ -60,7 +60,7 @@ Here is sample code demonstrating the approach: ```` -# See Also +## See Also * [RadPdfViewer documentation]({%slug pdfviewer/overview%}) diff --git a/knowledge-base/radajaxmanager-designer-does-not-locate-all-controls.md b/knowledge-base/radajaxmanager-designer-does-not-locate-all-controls.md index 1cc9816f62..b697a61c5e 100644 --- a/knowledge-base/radajaxmanager-designer-does-not-locate-all-controls.md +++ b/knowledge-base/radajaxmanager-designer-does-not-locate-all-controls.md @@ -34,50 +34,49 @@ To fix this issue and depending on your scenario, use any of the following appro The following example demonstrates how to set the `ID` for table cells of an `asp:Table` and set `runat='server'`. - ````ASP.NET - - - - - - - - - - - - - -
    - -
    -     - - -     -     - ```` - - After you have set the `ID` of the table cells and the `runat="server"` configuration, the designer can locate the button, check-box, and text box, and you can AJAXify the controls in the `asp:Table` cells as demonstrated by the following example. - - ````ASP.NET - - - - - - - - - - - - - - - - - ```` + ````ASP.NET + + + + + + + + + + + + + +
    + +
    +     + + +     +     + ```` + After you have set the `ID` of the table cells and the `runat="server"` configuration, the designer can locate the button, check-box, and text box, and you can AJAXify the controls in the `asp:Table` cells as demonstrated bythe following example. + + ````ASP.NET + + + + + + + + + + + + + + + + + ```` diff --git a/knowledge-base/raising-selectedindexchanged-server-side-radcombobox-multicolumncombobox.md b/knowledge-base/raising-selectedindexchanged-server-side-radcombobox-multicolumncombobox.md index 566d19087c..6863e39666 100644 --- a/knowledge-base/raising-selectedindexchanged-server-side-radcombobox-multicolumncombobox.md +++ b/knowledge-base/raising-selectedindexchanged-server-side-radcombobox-multicolumncombobox.md @@ -7,15 +7,15 @@ slug: raising-selectedindexchanged-server-side-radcombobox-multicolumncombobox tags: radcombobox, multicolumncombobox, selectedindexchanged, server-side, how-to res_type: kb --- -# Environment +## Environment | Product | Version | | --- | --- | | RadComboBox for ASP.NET AJAX | all | -# Description +## Description I want to raise the SelectedIndexChanged event server-side for RadComboBox and MultiColumnComboBox controls in my ASP.NET AJAX application. How can I achieve this? -# Solution +## Solution The SelectedIndexChanged event and similar events in web controls like RadComboBox and MultiColumnComboBox are designed to respond to user interactions in the browser. They are triggered when a user selects a new item from the drop-down list. However, programmatically changing the selection in server-side code does not automatically trigger the SelectedIndexChanged event. To programmatically set the selected value of a RadComboBox or MultiColumnComboBox and ensure that the SelectedIndexChanged event is fired server-side, you can use one of the following approaches: @@ -85,7 +85,7 @@ protected void Page_Load(object sender, EventArgs e) Remember, these workarounds mimic the behavior of the SelectedIndexChanged event and do not constitute an actual event firing as it would from a client-side action. Make sure to test thoroughly to ensure that your application behaves as expected. -# See Also +## See Also - [RadComboBox Documentation](https://docs.telerik.com/devtools/aspnet-ajax/controls/combobox/overview) - [MultiColumnComboBox Documentation](https://docs.telerik.com/devtools/aspnet-ajax/controls/multicolumncombobox/overview) diff --git a/knowledge-base/reversed-create-execution-order-ajax-manager-panel.md b/knowledge-base/reversed-create-execution-order-ajax-manager-panel.md index bab557143b..089ce52b2a 100644 --- a/knowledge-base/reversed-create-execution-order-ajax-manager-panel.md +++ b/knowledge-base/reversed-create-execution-order-ajax-manager-panel.md @@ -3,7 +3,7 @@ title: Using AjaxManager and AjaxPanel Causes Reversed Execution Order for the c page_title: Using AjaxManager and AjaxPanel Causes Reversed Execution Order for the create Control Function description: "Learn what to do when using the Telerik UI for ASP.NET AjaxManager and AjaxPanel leads to a reversed execution order of the create control function." slug: ajaxmanager/troubleshooting/tips-and-tricks-for-ajaxifying-specific-controls -previous_url: ajax/troubleshooting/tips-and-tricks-for-ajaxifying-specific-controls, controls/ajaxmanager/troubleshooting/tips-and-tricks-for-ajaxifying-specific-controls, controls/ajaxmanager/troubleshooting/tips-and-tricks-for-ajaxifying-specific-controls +previous_url: ajax/troubleshooting/tips-and-tricks-for-ajaxifying-specific-controls, controls/ajaxmanager/troubleshooting/tips-and-tricks-for-ajaxifying-specific-controls tags: telerik, asp, net, ajax, manager, panel, causes, reversed, execution, order, of, create, control, function published: True type: troubleshooting diff --git a/knowledge-base/scheduler-implement-related-radcombobox-controls-in-the-advanced-form.md b/knowledge-base/scheduler-implement-related-radcombobox-controls-in-the-advanced-form.md index d4a05e39fa..b99aaaa201 100644 --- a/knowledge-base/scheduler-implement-related-radcombobox-controls-in-the-advanced-form.md +++ b/knowledge-base/scheduler-implement-related-radcombobox-controls-in-the-advanced-form.md @@ -21,7 +21,7 @@ res_type: kb ## SOLUTION - 1. Download a demo project from [here](/community/code-library/aspnet-ajax/scheduler/customize-the-advanced-form-with-the-advanced-template-user-controls.aspx) and use the **SqlDataSource **sample. + 1. Download a demo project from [here](https://www.telerik.com/community/code-library/aspnet-ajax/scheduler/customize-the-advanced-form-with-the-advanced-template-user-controls.aspx) and use the **SqlDataSource **sample. 2. Create two new fields of type string for the DbProvider\_Classes - **Continent** and **Country**. The **TelerikVSX.mdf** file is in the App\_Data folder of the sample. diff --git a/knowledge-base/scheduler-integrating-radeditor-in-the-advanced-form-of-radscheduler.md b/knowledge-base/scheduler-integrating-radeditor-in-the-advanced-form-of-radscheduler.md index ad0c73e4c9..46efbe1f0c 100644 --- a/knowledge-base/scheduler-integrating-radeditor-in-the-advanced-form-of-radscheduler.md +++ b/knowledge-base/scheduler-integrating-radeditor-in-the-advanced-form-of-radscheduler.md @@ -25,7 +25,7 @@ res_type: kb ## SOLUTION - Download a working sample from [here](/support/kb/aspnet-ajax/scheduler/sample-project-of-the-customizing-the-advanced-template-example.aspx?) (SchedulerCustomAdvancedFormQ3\_SP1\_2009.zip). Then edit **AdvancedForm.ascx** to comment the description RadTextBox and add a RadEditor control and a description label like this: + Download a working sample from [here](https://www.telerik.com/support/kb/aspnet-ajax/scheduler/sample-project-of-the-customizing-the-advanced-template-example.aspx?) (SchedulerCustomAdvancedFormQ3\_SP1\_2009.zip). Then edit **AdvancedForm.ascx** to comment the description RadTextBox and add a RadEditor control and a description label like this: ````ASP.NET <%-- ' is incompatible with version 2.0.30625.9003 of NuGet. Please upgrade NuGet to the latest version. + Make sure that the Telerik NuGet Feed is live at [https://status.telerik.com/](https://status.telerik.com/). -In R1 2018, the `nuget.exe` version the suite uses was updated from `2.8` to `4.3`. This is the executable file used to generate and read the `.nupkg` files. +* The schema version of `` is incompatible with version 2.0.30625.9003 of NuGet. Please upgrade NuGet to the latest version. -Due to this update, you may get the error in question when using Visual Studio 2012 that uses the NuGet Package Manager version 2.0. To solve the problem, upgrade the NuGet Package Manager to version 2.8. + In R1 2018, the `nuget.exe` version the suite uses was updated from `2.8` to `4.3`. This is the executable file used to generate and read the `.nupkg` files. + + Due to this update, you may get the error in question when using Visual Studio 2012 that uses the NuGet Package Manager version 2.0. To solve the problem, upgrade the NuGet Package Manager to version 2.8. -### [Telerik NuGet] The V2 feed at 'https://nuget.telerik.com/nuget/Search()?$filter=IsLatestVersion&searchTerm='telerik'&targetFramework='net45'&includePrerelease=false&$skip=0&$top=26&semVerLevel=2.0.0' returned an unexpected status code '401 Logon failed.'. +* [Telerik NuGet] The V2 feed at 'https://nuget.telerik.com/nuget/Search()?$filter=IsLatestVersion&searchTerm='telerik'&targetFramework='net45'&includePrerelease=false&$skip=0&$top=26&semVerLevel=2.0.0' returned an unexpected status code '401 Logon failed.'. -To solve this issue, refer to the [nuget can't connect to Telerik NuGet Server](https://www.telerik.com/forums/nuget-can't-connect-to-https-nuget-telerik-com-nuget) forum thread. + To solve this issue, refer to the [nuget can't connect to Telerik NuGet Server](https://www.telerik.com/forums/nuget-can't-connect-to-https-nuget-telerik-com-nuget) forum thread. ## Additional Resources diff --git a/knowledge-base/window-printing-content.md b/knowledge-base/window-printing-content.md index 394522e4d2..5cd315f316 100644 --- a/knowledge-base/window-printing-content.md +++ b/knowledge-base/window-printing-content.md @@ -1,112 +1,112 @@ ---- -title: Printing the contents of a RadWindow -description: Printing the contents of a RadWindow. Check it now! -type: how-to -page_title: Printing the contents of a RadWindow -slug: window-printing-content -res_type: kb ---- - -## DESCRIPTION -RadWindow does not offer built-in printing functionality as regular browser popups do. There is also a difference whether an external page is loaded via the `NavigateUrl` or the `ContentTemplate` is used, as browser popups only load entire pages. - - -## SOLUTION -You ultimately need to rely on the `print()` command that the document and window objects provide. - ->note We cannot control the way this works, after `print()` is called the behavior is entirely controlled by the browser and the user machine's settings. -> - -There is also a difference how an external page and the `ContentTemplate` are handled. - -The external page creates an iframe, which also has its own document and window objects and you can use them directly to print the entire page from within this page by using the following JavaScript function: - -````JavaScript -if (document.all) -{ - document.execCommand("Print"); -} -else -{ - window.print(); -} -```` - -When the `ContentTemplate` is used the RadWindow's contents are part of the main page and we should not use its `print()` method directly, as this would print the entire page. We first need to take the contents of the RadWindow and then we can place them in a new browser popup, or a hidden iframe which provide the needed document and window objects: - -````ASP.NET - - -
    - . . . . . . -
    - -     -     -```` - -This is easiest done by wrapping the contents in a simple div so you can obtain its `innerHTML` and place it in a popup: - -````JavaScript -var content = $get("contentHolder").innerHTML; -var pwin = window.open('', 'print_content', 'width=300,height=300'); -pwin.document.open(); -pwin.document.write('' + content + ''); -pwin.document.close(); -setTimeout(function () { pwin.close(); }, 1000); -```` - -or use a predefined, hidden iframe on the page to avoid the popup: - -````HTML - -```` - -then you combine both approaches from below to provide the content and call its `print()` method: - -````JavaScript -var content = $get("contentHolder").innerHTML; - -var printIframe = $get("ifmcontentstoprint"); -var printDocument = printIframe.contentWindow.document; -printDocument.designMode = "on"; -printDocument.open(); -printDocument.write("" + content + ""); -printDocument.close(); -try -{ - if (document.all) - { - printDocument.execCommand("Print", null, false); - } - else - { - printIframe.contentWindow.print(); - } - -} -catch (ex) -{ - alert("error printing"); -} -```` - - - You may find useful [this KB article]({%slug window-adding-a-custom-button-to-radwindow-titlebar %}) on adding a custom button to the titlebar where you can attach the printing functionality. When working with external pages you would also need to call a function from the external page if you use a toolbar button, as its event is fired in the parent page. How to do this is explained in [this help article]({%slug window/how-to/calling-functions-in-windows %}). - - There is also a set of simple pages attached that shows this functionality in action: -* [custom-button-radwindow-after-q1-2016](files/custom-button-radwindow-after-q1-2016.zip.zip) - -* [custom-button-radwindow-after-q1-2016-xhtml-10-transitional](files/window-custom-button-radwindow-after-q1-2016-xhtml-10-transitional.zip.zip) - -* [custom-button-radwindow](files/custom-button-radwindow.zip.zip) - - - - - - - - - +--- +title: Printing the contents of a RadWindow +description: Printing the contents of a RadWindow. Check it now! +type: how-to +page_title: Printing the contents of a RadWindow +slug: window-printing-content +res_type: kb +--- + +## DESCRIPTION +RadWindow does not offer built-in printing functionality as regular browser popups do. There is also a difference whether an external page is loaded via the `NavigateUrl` or the `ContentTemplate` is used, as browser popups only load entire pages. + + +## SOLUTION +You ultimately need to rely on the `print()` command that the document and window objects provide. + +>note We cannot control the way this works, after `print()` is called the behavior is entirely controlled by the browser and the user machine's settings. +> + +There is also a difference how an external page and the `ContentTemplate` are handled. + +The external page creates an iframe, which also has its own document and window objects and you can use them directly to print the entire page from within this page by using the following JavaScript function: + +````JavaScript +if (document.all) +{ + document.execCommand("Print"); +} +else +{ + window.print(); +} +```` + +When the `ContentTemplate` is used the RadWindow's contents are part of the main page and we should not use its `print()` method directly, as this would print the entire page. We first need to take the contents of the RadWindow and then we can place them in a new browser popup, or a hidden iframe which provide the needed document and window objects: + +````ASP.NET + + +
    + . . . . . . +
    + +     +     +```` + +This is easiest done by wrapping the contents in a simple div so you can obtain its `innerHTML` and place it in a popup: + +````JavaScript +var content = $get("contentHolder").innerHTML; +var pwin = window.open('', 'print_content', 'width=300,height=300'); +pwin.document.open(); +pwin.document.write('' + content + ''); +pwin.document.close(); +setTimeout(function () { pwin.close(); }, 1000); +```` + +or use a predefined, hidden iframe on the page to avoid the popup: + +````HTML + +```` + +then you combine both approaches from below to provide the content and call its `print()` method: + +````JavaScript +var content = $get("contentHolder").innerHTML; + +var printIframe = $get("ifmcontentstoprint"); +var printDocument = printIframe.contentWindow.document; +printDocument.designMode = "on"; +printDocument.open(); +printDocument.write("" + content + ""); +printDocument.close(); +try +{ + if (document.all) + { + printDocument.execCommand("Print", null, false); + } + else + { + printIframe.contentWindow.print(); + } + +} +catch (ex) +{ + alert("error printing"); +} +```` + + + You may find useful [this KB article]({%slug window-adding-a-custom-button-to-radwindow-titlebar %}) on adding a custom button to the titlebar where you can attach the printing functionality. When working with external pages you would also need to call a function from the external page if you use a toolbar button, as its event is fired in the parent page. How to do this is explained in [this help article]({%slug window/how-to/calling-functions-in-windows %}). + + There is also a set of simple pages attached that shows this functionality in action: +* [custom-button-radwindow-after-q1-2016](files/custom-button-radwindow-after-q1-2016.zip) + +* [custom-button-radwindow-after-q1-2016-xhtml-10-transitional](files/window-custom-button-radwindow-after-q1-2016-xhtml-10-transitional.zip) + +* [custom-button-radwindow](files/custom-button-radwindow.zip) + + + + + + + + + diff --git a/licensing.md b/licensing.md index 52131d8b71..e5e296abb5 100644 --- a/licensing.md +++ b/licensing.md @@ -1,55 +1,54 @@ ---- -title: Licensing -page_title: Licensing -description: "Learn more about the trial and commercial licenses, the .NET licensing mechanism, and the license limitations by Telerik UI for ASP.NET AJAX." -slug: introduction/licensing/license-agreement -previous_url: licensing/licensing -tags: license, agreement -previous_url: licensing/license-agreement, licensing/trial-license-limitations, licensing/license-file -published: True -position: 20 ---- - -# Licensing - -Telerik UI for ASP.NET AJAX offers a 30-day trial with a full-featured version of the tool—no restrictions! What’s more, you are eligible for complete technical support during your trial period in case you have any questions. To sign up for a free 30-day trial, go [here](https://www.telerik.com/login-b/ui-for-asp.net-ajax#register). - -To use Telerik UI for ASP.NET AJAX commercially, you need to purchase a license. The terms of use are fully described in the [Telerik UI for ASP.NET AJAX End User License Agreement (EULA)](https://www.telerik.com/purchase/license-agreement/aspnet-ajax). The EULA is also available in your Telerik controls installation folder under `\LicenseAgreements\EULA.rtf`. For example, the default location for the R2 2018 release is `C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX R2 2018\LicenseAgreements\EULA.rtf`. - -## License Limitations - -Developer licenses come with modified DLLs, which work without displaying copyright messages. If you have a Developer license for one or more Telerik components, you need to ensure that you are using the developer build when downloading the controls. These builds have the `Dev` abbreviation in their file names. - -If your application is displaying a copyright message intermittently, this means that you are using a trial version of the product. Log in to your [Telerik account](https://www.telerik.com/account/default.aspx) and download the developer build through the **Products & Subscriptions** menu and its **Purchased Products** section. For more information on updating your project, refer to the article on the [Upgrading the Trial License to a Production License]({%slug introduction/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version%}) section for step-by-step instructions. - -The free trial licenses of all Telerik products are fully functional and will work for an unlimited time, but will randomly display a copyright message on the page. - -## Bill of Materials and Third-Party Software Licensing - -For a Bill of Materials (BOM) and a list of the third party software (including open-source software), go to your Telerik controls installation folder `\LicenseAgreements\ThirdParty\NOTICE.txt`. For example, the default location for the R2 2018 SP1 release is `C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX R2 2018\LicenseAgreements\ThirdParty\NOTICE.txt`. For versions prior to R2 2018 SP1, the file is called `licenses.txt`. - -## .NET Licensing Mechanism - -As of Q1 2015, Telerik UI for ASP.NET AJAX uses the [standard .NET licensing mechanism](https://docs.microsoft.com/bg-bg/dotnet/framework/tools/lc-exe-license-compiler), which means that using the controls in design-time causes Visual Studio to add a `license.licx` to the solution. This file is used only in design-mode and is not needed for deployment explicitly. The .NET framework (`lc.exe`) will embed it in the assembly when your web application is built for deployment. - -The `license.licx` file is maintained by Visual Studio and contains information about all licensed components in the application, including non-Telerik products. The availability of this license file is not expected to cause any performance or compilation issues and you can ignore it. - -* If your project build fails with errors pointing to the license file, you can delete it and rebuild the application. Alternatively, you can clear its contents and mark it as `Read Only`. All known errors related to the usage of the license file are covered by the KB article on [fixing license file related errors]({% slug common-how-to-fix-license-file-related-errors %}). - -* If you are working under source control, once the file is created, it will be detected as a change by your source control system. It is recommended that you check in this file initially. When the files is checked out again during your work, it is up to you to decide whether to check it in or discard the changes. - -* If you are getting random copyright errors in the browser when using the trial version of Telerik UI for ASP.NET AJAX, refer to the article on [getting the copyright message]({% slug introduction/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version %}}#i-still-get-the-copyright-message). In this case, you need to upgrade the `Telerik.Web.UI.dll` trial version with the registered developer one as explained in the article on [upgrading a trial to a developer license]({% slug introduction/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version %}#upgrade-from-trial-to-licensed-version-of-telerik-ui-for-aspnet-ajax). - -## Licensing FAQ - -* *How many licenses do I need?* - Each license allows one developer to work with the product. If you purchase a license for a product bundle, such as Telerik UI for ASP.NET AJAX or DevCraft Complete, all the tools in the bundle are licensed to one developer, and only that developer can develop products with the tools in the bundle. - -* *Can I install the product on more than one machine?* - The Telerik licenses have no ties to any specific machine or server, but only to a developer. Developers can install an application that uses our controls on one to many machines (development, staging, production) using their single license. - -* *Does the trial version impose any limitations?* - The trial version of Telerik UI for ASP.NET AJAX is fully functional and will continue to work even after the 30 days evaluation period. The only limitation is the random trial error message that you will get sometimes when you refresh or load the page with the components. The upgrade to a registered Dev version of the product will remove the trial error. You can find upgrade instructions in [Upgrade From Trial to Licensed Version of Telerik® UI for ASP.NET AJAX]({% slug introduction/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version %}). - -You can find more information for the licensing in the [Purchasing & Licensing FAQs](https://www.telerik.com/purchase/faq/licensing-purchasing) page as well as in the [Telerik licensing demystified](https://www.telerik.com/blogs/telerik-licensing-demystified) blog post. - - - - +--- +title: Licensing +page_title: Licensing +description: "Learn more about the trial and commercial licenses, the .NET licensing mechanism, and the license limitations by Telerik UI for ASP.NET AJAX." +slug: introduction/licensing/license-agreement +tags: license, agreement +previous_url: licensing/license-agreement, licensing/trial-license-limitations, licensing/license-file +published: True +position: 20 +--- + +# Licensing + +Telerik UI for ASP.NET AJAX offers a 30-day trial with a full-featured version of the tool—no restrictions! What’s more, you are eligible for complete technical support during your trial period in case you have any questions. To sign up for a free 30-day trial, go [here](https://www.telerik.com/login-b/ui-for-asp.net-ajax#register). + +To use Telerik UI for ASP.NET AJAX commercially, you need to purchase a license. The terms of use are fully described in the [Telerik UI for ASP.NET AJAX End User License Agreement (EULA)](https://www.telerik.com/purchase/license-agreement/aspnet-ajax). The EULA is also available in your Telerik controls installation folder under `\LicenseAgreements\EULA.rtf`. For example, the default location for the R2 2018 release is `C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX R2 2018\LicenseAgreements\EULA.rtf`. + +## License Limitations + +Developer licenses come with modified DLLs, which work without displaying copyright messages. If you have a Developer license for one or more Telerik components, you need to ensure that you are using the developer build when downloading the controls. These builds have the `Dev` abbreviation in their file names. + +If your application is displaying a copyright message intermittently, this means that you are using a trial version of the product. Log in to your [Telerik account](https://www.telerik.com/account/default.aspx) and download the developer build through the **Products & Subscriptions** menu and its **Purchased Products** section. For more information on updating your project, refer to the article on the [Upgrading the Trial License to a Production License]({%slug introduction/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version%}) section for step-by-step instructions. + +The free trial licenses of all Telerik products are fully functional and will work for an unlimited time, but will randomly display a copyright message on the page. + +## Bill of Materials and Third-Party Software Licensing + +For a Bill of Materials (BOM) and a list of the third party software (including open-source software), go to your Telerik controls installation folder `\LicenseAgreements\ThirdParty\NOTICE.txt`. For example, the default location for the R2 2018 SP1 release is `C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX R2 2018\LicenseAgreements\ThirdParty\NOTICE.txt`. For versions prior to R2 2018 SP1, the file is called `licenses.txt`. + +## .NET Licensing Mechanism + +As of Q1 2015, Telerik UI for ASP.NET AJAX uses the [standard .NET licensing mechanism](https://docs.microsoft.com/bg-bg/dotnet/framework/tools/lc-exe-license-compiler), which means that using the controls in design-time causes Visual Studio to add a `license.licx` to the solution. This file is used only in design-mode and is not needed for deployment explicitly. The .NET framework (`lc.exe`) will embed it in the assembly when your web application is built for deployment. + +The `license.licx` file is maintained by Visual Studio and contains information about all licensed components in the application, including non-Telerik products. The availability of this license file is not expected to cause any performance or compilation issues and you can ignore it. + +* If your project build fails with errors pointing to the license file, you can delete it and rebuild the application. Alternatively, you can clear its contents and mark it as `Read Only`. All known errors related to the usage of the license file are covered by the KB article on [fixing license file related errors]({% slug common-how-to-fix-license-file-related-errors %}). + +* If you are working under source control, once the file is created, it will be detected as a change by your source control system. It is recommended that you check in this file initially. When the files is checked out again during your work, it is up to you to decide whether to check it in or discard the changes. + +* If you are getting random copyright errors in the browser when using the trial version of Telerik UI for ASP.NET AJAX, refer to the article on [getting the copyright message]({% slug introduction/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version %}#i-still-get-the-copyright-message). In this case, you need to upgrade the `Telerik.Web.UI.dll` trial version with the registered developer one as explained in the article on [upgrading a trial to a developer license]({% slug introduction/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version %}#upgrade-from-trial-to-licensed-version-of-telerik-ui-for-aspnet-ajax). + +## Licensing FAQ + +* *How many licenses do I need?* - Each license allows one developer to work with the product. If you purchase a license for a product bundle, such as Telerik UI for ASP.NET AJAX or DevCraft Complete, all the tools in the bundle are licensed to one developer, and only that developer can develop products with the tools in the bundle. + +* *Can I install the product on more than one machine?* - The Telerik licenses have no ties to any specific machine or server, but only to a developer. Developers can install an application that uses our controls on one to many machines (development, staging, production) using their single license. + +* *Does the trial version impose any limitations?* - The trial version of Telerik UI for ASP.NET AJAX is fully functional and will continue to work even after the 30 days evaluation period. The only limitation is the random trial error message that you will get sometimes when you refresh or load the page with the components. The upgrade to a registered Dev version of the product will remove the trial error. You can find upgrade instructions in [Upgrade From Trial to Licensed Version of Telerik® UI for ASP.NET AJAX]({% slug introduction/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version %}). + +You can find more information for the licensing in the [Purchasing & Licensing FAQs](https://www.telerik.com/purchase/faq/licensing-purchasing) page as well as in the [Telerik licensing demystified](https://www.telerik.com/blogs/telerik-licensing-demystified) blog post. + + + + diff --git a/shared-utilities/browser-detection-api.md b/shared-utilities/browser-detection-api.md index b6270bc17a..e11b02b7a9 100644 --- a/shared-utilities/browser-detection-api.md +++ b/shared-utilities/browser-detection-api.md @@ -159,4 +159,4 @@ Here is one example that shows how you can use these flags. The script is after * [Telerik.Web.Platform]({%slug Telerik.Web.Platform%}) -* [Telerik.Web.Browser]({%slug Telerik.Web.Browser%}.html) +* [Telerik.Web.Browser]({%slug Telerik.Web.Browser%}) diff --git a/upgrade-compatibility/changes-and-backwards-compatibility.md b/upgrade-compatibility/changes-and-backwards-compatibility.md index cab056aa56..6ca8343b8a 100644 --- a/upgrade-compatibility/changes-and-backwards-compatibility.md +++ b/upgrade-compatibility/changes-and-backwards-compatibility.md @@ -5,7 +5,6 @@ description: Check our Web Forms article about Changes and Backwards Compatibili slug: controls/changes-and-backwards-compatibility previous_url: what's-new-and-backwards-compatibility, general-information/changes-and-backwards-compatibility tags: changes,and,backwards,compatibility -previous_url: controls/changes-and-backwards-compatibility published: True position: 9 --- diff --git a/upgrade-compatibility/fips-compatibility.md b/upgrade-compatibility/fips-compatibility.md index 9150bf3b4f..116b7d1de4 100644 --- a/upgrade-compatibility/fips-compatibility.md +++ b/upgrade-compatibility/fips-compatibility.md @@ -4,9 +4,8 @@ page_title: FIPS Compatibility description: Check our Web Forms article about FIPS Compatibility. slug: controls/fips-compatibility tags: fips, compatibility -previous_url: general-information/fips-compatibility +previous_url: general-information/fips-compatibility, controls/fips-compatibility published: True -previous_url: controls/fips-compatibility position: 10 ---