diff --git a/.gitignore b/.gitignore index f52a149307..eb3e7a0865 100644 --- a/.gitignore +++ b/.gitignore @@ -14,11 +14,11 @@ /_includes/ /_layouts/ /_plugins/ -/_templates/ /docs-watcher/ /favicon.ico /fonts/ /styles/ +_templates CODEOWNERS Dockerfile Gemfile @@ -27,6 +27,7 @@ SlugLog.log _excludefile.yml _site _tempconfig.yml +_tools bs-config.js build-docs.sh copy_content.sh diff --git a/_templates/common/additional-libraries-path.md b/_templates/common/additional-libraries-path.md index a6df4618dc..96f8261df7 100644 --- a/_templates/common/additional-libraries-path.md +++ b/_templates/common/additional-libraries-path.md @@ -1,3 +1,3 @@ #additional-libraries-path -You can access @{assemblies} from the `AdditionalLibraries` folder in the **Telerik® UI for ASP.NET AJAX** installation (automated and manual) and from the internal builds archive. @{support} .NET 4 and .NET 4.5, so depending on the target framework of your project, you need to take the @{isplural} from the `Bin40` or the `Bin45` folder respectively. +You can access @{assemblies} from the `AdditionalLibraries` folder in the **Telerik® UI for ASP.NET AJAX** installation (automated and manual) and from the internal builds archive. @{support} .NET 4 and .NET 4.5, so depending on the target framework of your project, you need to take the @{isplural} from the `Bin40` or the `Bin45` or the `Bin462` folder respectively. #end diff --git a/deployment/using-the-global-assembly-cache.md b/deployment/using-the-global-assembly-cache.md index 38bb87fe94..7fef4fa10d 100644 --- a/deployment/using-the-global-assembly-cache.md +++ b/deployment/using-the-global-assembly-cache.md @@ -118,9 +118,9 @@ To install an assembly called SomeAssembly in the GAC, use the command `gacutil /i "C:\someFolder\SomeAssembly.dll"` -Here is an example that adds the R3 2017 Telerik.Web.UI.dll assembly to the GAC: +Here is an example that adds the Q2 2024 Telerik.Web.UI.dll assembly to the GAC: -`gacutil /i "C:\Program Files\Progress\UI for ASP.NET AJAX R3 2017\Bin45\Telerik.Web.UI.dll"` +`gacutil /i "C:\Program Files\Progress\Telerik UI for ASP.NET AJAX 2024 Q2\Bin462\Telerik.Web.UI.dll"` There are other ways to add an assembly to the GAC (Windows offers a shell integration for .NET 3.5 so you can just drag-and-drop it; and the Windows Installer) but since the gacutil tool is available for standalone download without Visual Studio, it is the more general way that works on all .NET versions. Note that Microsoft do not recommend using gacutil in production environment. diff --git a/getting-started/first-steps-zip.md b/getting-started/first-steps-zip.md index 73ca6b0d01..6e3aea3328 100644 --- a/getting-started/first-steps-zip.md +++ b/getting-started/first-steps-zip.md @@ -60,7 +60,7 @@ The files from the ZIP installation are usually used for manual upgrading of an 1. Open the **Bin** folder of your project in Windows Explorer and delete the old `Telerik.Web.UI.*` assemblies. -1. Copy the new assemblies from the `Bin45` folder in the UI for ASP.NET AJAX installation path and paste them to the `Bin` folder of your project. +1. Copy the new assemblies from the `Bin462` folder in the UI for ASP.NET AJAX installation path and paste them to the `Bin` folder of your project. You can use the copy-and-replace method to upgrade any [other assemblies]({%slug introduction/installation/included-assemblies%}), localization files (`~/App_GlobalResources`), dialogs (ImageEditor, Editor), [TypeScript definitions]({%slug introduction/radcontrols-for-asp.net-ajax-fundamentals/integration-with-visual-studio/typescript-definitions/add-typescript-definitions-for-the-telerik-ui-for-asp.net-ajax-suite%}), and so on. diff --git a/getting-started/installation/included-assemblies.md b/getting-started/installation/included-assemblies.md index 090912f076..667fa7a5d6 100644 --- a/getting-started/installation/included-assemblies.md +++ b/getting-started/installation/included-assemblies.md @@ -19,7 +19,7 @@ The assemblies come sorted in several folders so that you can use the ones you n * If you target `.NET 3.5`, use the assemblies from the `Bin35` folder ([distributed until R1 2023 SP1](https://www.telerik.com/support/whats-new/aspnet-ajax/release-history/ui-for-asp-net-ajax-r1-2023-sp1-(version-2023-1-314))). * If you target `.NET 4.0`, use the assemblies from the `Bin40` folder ([distributed until R1 2023 SP1](https://www.telerik.com/support/whats-new/aspnet-ajax/release-history/ui-for-asp-net-ajax-r1-2023-sp1-(version-2023-1-314))). * If you target `.NET 4.5`, `.NET 4.6`, or `.NET 4.6.1` use the assemblies from the `Bin45` folder ([distributed until 2024 Q1](https://www.telerik.com/support/whats-new/aspnet-ajax/release-history/ui-for-asp-net-ajax-2024-q1-(version-2024-1-131))). -* If you target `.NET 4.6.2`, `.NET 4.7`, `.NET 4.7.1`, `.NET 4.7.2`, `.NET 4.8`, or `.NET 4.8.1`, use the assemblies from the `Bin46` folder. This folder will be available starting with the 2024 Q2 release on May 15, 2024. +* If you target `.NET 4.6.2`, `.NET 4.7`, `.NET 4.7.1`, `.NET 4.7.2`, `.NET 4.8`, or `.NET 4.8.1`, use the assemblies from the `Bin462` folder. This folder will be available starting with the 2024 Q2 release on May 15, 2024. The binaries from the `Additional Assemblies` folder may have different versions from the main assemblies. You have to use the assemblies from the same release as the main assemblies. diff --git a/integration/visual-studio/adding-the-telerik-controls-to-the-visual-studio-toolbox.md b/integration/visual-studio/adding-the-telerik-controls-to-the-visual-studio-toolbox.md index 08fe4e7fcb..fb038b3fc5 100644 --- a/integration/visual-studio/adding-the-telerik-controls-to-the-visual-studio-toolbox.md +++ b/integration/visual-studio/adding-the-telerik-controls-to-the-visual-studio-toolbox.md @@ -25,20 +25,20 @@ If you are installing Telerik UI for ASP.NET AJAX from a [ZIP distribution]({%sl 1. Expand the Toolbox. -1. Expand the **General** section. Alternatively, you can create a new section by selecting the **Add Tab** option from the context menu (right click anywhere in the toolbox). When the new tab is added you can choose its name (e.g. Telerik UI for ASP.NET AJAX RX YYYY). +1. Expand the **General** section. Alternatively, you can create a new section by selecting the **Add Tab** option from the context menu (right click anywhere in the toolbox). When the new tab is added you can choose its name (e.g. Telerik UI for ASP.NET AJAX YYYY QX). 1. Right-click in the **General** section (or the new one you just created) and open **Choose Items**. ![Choose Items in Visual Studio Toolbox](images/manual_add_telerik_controls_to_VS_toolbox.gif) 1. On the **.NET Framework Components** tab, click **Browse**. -1. Browse to the installation folder, open the **Bin45** folder and select the **Telerik.Web.UI.dll**. +1. Browse to the installation folder, open the **Bin462** folder and select the **Telerik.Web.UI.dll**. - * If the Windows Installer MSI Package was used to install Telerik UI for ASP.NET AJAX, the **bin45** folder is located in **C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX RX YYYY\Bin45**. If this folder is missing, download the hotfix installation and obtain the Telerik.Web.UI.dll assembly from it as instructed in point 1 in the above list. + * If the Windows Installer MSI Package was used to install Telerik UI for ASP.NET AJAX, the **Bin462** folder is located in **C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX YYYY QX\Bin462**. If this folder is missing, download the hotfix installation and obtain the Telerik.Web.UI.dll assembly from it as instructed in point 1 in the above list. - * If the ZIP was used to install the Telerik controls, the **Bin45** folder is located in the folder where the installation files have been unzipped. + * If the ZIP was used to install the Telerik controls, the **Bin462** folder is located in the folder where the installation files have been unzipped. - >note If you want to add Telerik controls for .NET 3.5 or .NET 4.0 web project you should select the Telerik.Web.UI.dll from the **C:\Program Files (x86)\Progress\UI for ASP.NET AJAX RX YYYY\Bin35** or **~/Bin40** folder. Note that both Bin35 and Bin40 folders are [distributed until R1 2023 SP1](https://www.telerik.com/support/whats-new/aspnet-ajax/release-history/ui-for-asp-net-ajax-r1-2023-sp1-(version-2023-1-314). + >note If you want to add Telerik controls for .NET 3.5, .NET 4.0 or .NET 4.5 web project you should select the Telerik.Web.UI.dll from the **C:\Program Files (x86)\Progress\UI for ASP.NET AJAX RX YYYY\Bin35** or **~/Bin40** or **~/Bin45** folder. Note that Bin35 and Bin40 folders are [distributed until R1 2023 SP1](https://www.telerik.com/support/whats-new/aspnet-ajax/release-history/ui-for-asp-net-ajax-r1-2023-sp1-(version-2023-1-314) and Bin45 is [distributed until 2024 Q1](https://www.telerik.com/support/whats-new/aspnet-ajax/release-history/ui-for-asp-net-ajax-2024-q1-(version-2024-1-131)). ## Troubleshooting diff --git a/knowledge-base/common-how-to-fix-license-file-related-errors.md b/knowledge-base/common-how-to-fix-license-file-related-errors.md index 856f8f8b55..a72cba1846 100644 --- a/knowledge-base/common-how-to-fix-license-file-related-errors.md +++ b/knowledge-base/common-how-to-fix-license-file-related-errors.md @@ -59,7 +59,7 @@ or Could not load file or assembly 'Telerik.Web.UI, Version=20xx.x.xxx.xx, Culture=neutral, PublicKeyToken=121fae78165ba3d4' or one of its dependencies. Invalid pointer (Exception from HRESULT: 0x80004003 (E_POINTER))' you can solve them by: - * Since the error could happen if the installed .NET Runtime assemblies are different than the project's configured .NET Runtime (targetFramework), make sure that the targetFramework of the app matches the .NET version of the Telerik Web UI assemblies. If the app is built against .NET 4.0, use the Telerik assemblies built for .NET 4.0 (in the manual installation they reside inside the Bin40 folder, for NET 4.5 and above, use the assemblies in the Bin45 folder). One way to test if this is the cause of the issue is to double-click on the error in the Visual Studio Output window which will open the file with the error. Upon opening the file, Visual Studio will then do some thinking and then the error will disappear. + * Since the error could happen if the installed .NET Runtime assemblies are different than the project's configured .NET Runtime (targetFramework), make sure that the targetFramework of the app matches the .NET version of the Telerik Web UI assemblies. If the app is built against .NET 4.0, use the Telerik assemblies built for .NET 4.0 (in the manual installation they reside inside the Bin40 folder, for .NET 4.5, .NET 4.6, or .NET 4.6.1 use the assemblies from the Bin45 folder, and for .NET 4.6.2, .NET 4.7, .NET 4.7.1, .NET 4.7.2, .NET 4.8, or .NET 4.8.1 use the assemblies in the Bin462 folder). One way to test if this is the cause of the issue is to double-click on the error in the Visual Studio Output window which will open the file with the error. Upon opening the file, Visual Studio will then do some thinking and then the error will disappear. * Another reason for the error is the existence of old versions of the Telerik assemblies declared inside the licenses.licx file. Open the file and Delete the contents of the license.licx and making it read only. * Alternatively, you can also delete the whole license.licx file and rebuild * Or right-click the Telerik.Web.UI.dll file in Windows Explorer, select Properties, and then click the 'Unblock' button on the General tab near the bottom. diff --git a/knowledge-base/common_assembly_exists_in_both_the_file_system_and_in_gac.md b/knowledge-base/common_assembly_exists_in_both_the_file_system_and_in_gac.md index 41746e93e2..3edf5c917f 100644 --- a/knowledge-base/common_assembly_exists_in_both_the_file_system_and_in_gac.md +++ b/knowledge-base/common_assembly_exists_in_both_the_file_system_and_in_gac.md @@ -32,7 +32,7 @@ Upon using the Telerik Extension to Upgrade the Assemblies, the Assemblies at bo ## Error Messages * "The assembly C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX RX 20XX\BinXX\..\AdditionalLibraries\BinXX\Telerik.Documents.SpreadsheetStreaming.dll exists in both the file system and in GAC. WebSites always use the version in GAC when a duplicate entry found. You could remove the assembly from GAC and reconfigure the WebSite if you need a bin-deployed assembly." -* "The assembly C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX R2 2022\Bin45\..\AdditionalLibraries\Bin45\Telerik.Windows.Documents.Spreadsheet.dll exists in both the file system and in GAC. WebSites always use the version in GAC when a duplicate entry found. You could remove the assembly from GAC and reconfigure the WebSite if you need a bin-deployed assembly" +* "The assembly C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX 2024 Q2\Bin462\..\AdditionalLibraries\Bin462\Telerik.Windows.Documents.Spreadsheet.dll exists in both the file system and in GAC. WebSites always use the version in GAC when a duplicate entry found. You could remove the assembly from GAC and reconfigure the WebSite if you need a bin-deployed assembly" * "The assembly Path_To_Telerik_Assembly_Installation_Folder]\BinXX\..\AdditionalLibraries\BinXX\Telerik.[AssemblyName].dll exists in both the file system and in GAC. WebSites always use the version in GAC when a duplicate entry found. You could remove the assembly from GAC and reconfigure the WebSite if you need a bin-deployed assembly." ## Solution diff --git a/knowledge-base/unknown-server-tag-could-not-load-file-or-assembly.md b/knowledge-base/unknown-server-tag-could-not-load-file-or-assembly.md index 2d88d83cfd..e3d12b0c28 100644 --- a/knowledge-base/unknown-server-tag-could-not-load-file-or-assembly.md +++ b/knowledge-base/unknown-server-tag-could-not-load-file-or-assembly.md @@ -63,7 +63,7 @@ To solve this issue, use the respective approach: * Update the `Bin` reference: - 1. Browse to the `Telerik.Web.UI` assembly through the **Property** pages. Make sure to choose the assembly from the correct folder (e.g. `bin35`, `bin40` or `bin45`) depening on the .NET version of your project. + 1. Browse to the `Telerik.Web.UI` assembly through the **Property** pages. Make sure to choose the assembly from the correct folder (e.g. `bin35`, `bin40`, `bin45` or `bin462`) depening on the .NET version of your project. ![Browser to reference](images/introduction-browse_to_reference.png) diff --git a/upgrade-compatibility/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version.md b/upgrade-compatibility/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version.md index 9176f28d7a..fbf679496d 100644 --- a/upgrade-compatibility/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version.md +++ b/upgrade-compatibility/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version.md @@ -53,7 +53,9 @@ The following steps ensure a safe upgrade: 1. Copy the new assemblies from the corresponding `Bin*` folder in the UI for ASP.NET AJAX installation path: - * The `Bin45` folder contains the assemblies for .NET 4.5 and above. + * **Bin462**: Contains the assemblies for .NET 4.6.2 and above. + + * **Bin45**: Contains the assemblies for .NET 4.5 ([distributed until 2024 Q1](https://www.telerik.com/support/whats-new/aspnet-ajax/release-history/ui-for-asp-net-ajax-2024-q1-(version-2024-1-131))). * The `Bin40` folder contains the assemblies for .NET 4.0 ([distributed until R1 2023 SP1](https://www.telerik.com/support/whats-new/aspnet-ajax/release-history/ui-for-asp-net-ajax-r1-2023-sp1-(version-2023-1-314))).