Skip to content

Commit 1354652

Browse files
authored
Update adding-radcontrols-to-visual-studio-toolbox.md
1 parent 5402bf4 commit 1354652

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

visual-studio-integration/adding-radcontrols-to-visual-studio-toolbox.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Adding RadControls to Visual Studio Toolbox in .NET Framework Projects
33
page_title: Adding RadControls to Visual Studio Toolbox
4-
description: Telerik UI for WinForms are automatically added to Visual Studio Toolbox during installation. But there are also two ways to manually do that.
4+
description: Telerik UI for WinForms is automatically added to Vthe isual Studio Toolbox during installation. But there are also two ways to manually do that.
55
slug: winforms/installation-deployment-and-distribution/adding-radcontrols-to-visual-studio-toolbox
66
tags: adding,radcontrols,to,visual,studio,toolbox,net framework
77
published: True
@@ -38,7 +38,7 @@ Telerik UI for WinForms are automatically added to Visual Studio 2019/2022 Toolb
3838

3939
1. Run Visual Studio.
4040

41-
1. Open any windows forms project/solution.
41+
1. Open any Windows Forms project/solution.
4242

4343
1. Expand the Toolbox.
4444

@@ -59,15 +59,15 @@ __Telerik assemblies do not appear in Visual Studio's Add reference dialog__
5959

6060
Make sure that the Telerik WinForms controls are added in the Global Assembly Cache (GAC) as described in the [Add/Remove RadControls to the Global Assembly Cache (GAC)]({%slug winforms/installation-deployment-and-distribution/application-deploymentadd-remove-radcontrols-to-the-global-assembly-cache-(gac)%}) topic.
6161

62-
__Telerik assemblies do not appear in Visual Studio's Add reference dialog although they are added in the GAC__
62+
__Telerik assemblies do not appear in Visual Studio's Add reference dialog, although they are added in the GAC__
6363

6464
To display your assembly in the __Add Reference__ dialog box, you can add a registry key, such as the following, which points to the location of the assembly:
6565

6666
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\AssemblyFolders\Telerik UI for WinForms Q1 2014]@="C:\Program Files\Telerik\UI for WinForms\Q1 2014\bin\"
6767

6868
Change this according to your installation and version specifics. Restart Visual Studio .NET after you have added the key.
6969

70-
> note You can create the this registry entry under the __HKEY_LOCAL_MACHINE__ hive. This will change the setting for all of the users on the system. If you create this registry entry under __HKEY_CURRENT_USER__, this entry will affect the setting for only the current user. 
70+
> note You can create this registry entry under the __HKEY_LOCAL_MACHINE__ hive. This will change the setting for all of the users on the system. If you create this registry entry under __HKEY_CURRENT_USER__, this entry will affect the setting for only the current user. 
7171
7272
More information about this topic you could find in Microsoft Support Center: [How to display an assembly in the "Add Reference" dialog box](http://support.microsoft.com/?kbid=306149)
7373

@@ -89,7 +89,7 @@ Below are the different kinds of occurrences and their possible fixes:
8989

9090
* Right-click the Toolbox inside Visual Studio and click Reset
9191

92-
* Multiple entries per control, number increasing with each start of the IDE: this is the worst scenario we have come across. All the registry entries and files on the customer machine seemed fine in this case. The only fix we were able to apply was a complete uninstall of Telerik UI for WinForms and Visual Studio 2010, followed by a clean install of the IDE and the suite.
92+
* Multiple entries per control, number increasing with each start of the IDE: this is the worst scenario we have come across. All the registry entries and files on the customer machine seemed fine in this case. The only fix we were able to apply was a complete uninstall of Telerik UI for WinForms and Visual Studio 2022, followed by a clean install of the IDE and the suite.
9393

9494
## See Also
9595

0 commit comments

Comments
 (0)