Deployment and General Information articles fixes

Author: kdikov82

deployment/deploying-a-telerik-enabled-webapplication.md

@@ -18,10 +18,11 @@ Deploying an application that uses the Telerik UI for ASP.NET AJAX controls is d
 
 To ensure a successful deployment, you need to check the following items:
 
-* For the controls to be recognized by the server, the application must properly reference the Telerik.Web.UI.dll assembly.The [Included Assemblies]({%slug introduction/installation/included-assemblies%}) help article explains where you can find thefile(s) that you need.
+* For the controls to be recognized by the server, the application must properly reference the Telerik.Web.UI.dll assembly.The [Included Assemblies]({%slug introduction/installation/included-assemblies%}) help article explains where you can find the file(s) that you need.
 
-* Make sure that the needed assemblies are copied over to the production server. This often involves setting the *CopyLocal*property of the WebApplication reference to *true*. In case you are deploying the assemblies in the GAC, examine the[Working with Assemblies in the GAC](http://blogs.telerik.com/aspnet-ajax/posts/13-09-19/working-with-assemblies-in-the-global-assembly-cache)blog post.
+* Make sure that the needed assemblies are copied over to the production server. This often involves setting the *CopyLocal* property of the WebApplication reference to *true*. In case you are deploying the assemblies in the GAC, examine the [Working with Assemblies in the GAC](http://blogs.telerik.com/aspnet-ajax/posts/13-09-19/working-with-assemblies-in-the-global-assembly-cache) blog post.
 
 * Make sure that the needed additions are made to the web.config on the production server. The[web.config Settings Overview]({%slug general-information/web-config-settings-overview%}) article lists them.
 
-* Make sure that the MS AJAX extensions are installed on the production server. You can find more information about them at[http://www.asp.net/AJAX/Documentation/Live/InstallingASPNETAJAX.aspx](http://www.asp.net/AJAX/Documentation/Live/InstallingASPNETAJAX.aspx).
+* Make sure that the MS AJAX extensions are installed on the production server. You can find more information about them at [http://www.asp.net/AJAX/Documentation/Live/InstallingASPNETAJAX.aspx](http://www.asp.net/AJAX/Documentation/Live/InstallingASPNETAJAX.aspx).
+ 

deployment/deploying-on-shared-hosting.md

@@ -30,19 +30,19 @@ All Telerik controls are server controls and have to be installed on the web ser
 
 1. Remember the application name and click OK.
 
-1. Give full permissions to the __ASPNET__ user (if you are using IIS5) or to the __Network Service__ account (using IIS6 or IIS7, Windows Server 2003, Windows Vista/Longhorn) on the application folder. Again, before doing this step, consult with your hosting provider on how this is to be accomplished. If the provider offers thorough instructions, use them instead of the ones below. Otherwise, contact your provider to set the permissions for you.
+1. Give full permissions to the **ASPNET** user (if you are using IIS5) or to the **Network Service** account (using IIS6 or IIS7, Windows Server 2003, Windows Vista/Longhorn) on the application folder. Again, before doing this step, consult with your hosting provider on how this is to be accomplished. If the provider offers thorough instructions, use them instead of the ones below. Otherwise, contact your provider to set the permissions for you.
 
 1. Run the project.
 
 ## If you plan to deploy the controls directly on the shared hosting
 
-1. Log into your [Telerik account](http://www.telerik.com/account/default.aspx) and click on __Manage products__ from the top menu.
+1. Log into your [Telerik account](http://www.telerik.com/account/default.aspx) and click on **Manage products** from the top menu.
 
-1. In the dropdown that appears choose from your purchased products or trial downloads the Telerik UI for ASP.NET AJAX, and click on it. If you have purchased a collection you would need to click on it and the trial downloads page will show all trial downlads directly.
+1. In the dropdown that appears choose from your purchased products or trial downloads the Telerik UI for ASP.NET AJAX, and click on it. If you have purchased a collection you would need to click on it and the trial downloads page will show all trial downloads directly.
 
-1. Click on __Download Installer and other resources__ (the Download link next to the suite if you are a trial user). You need to choose the Telerik UI for ASP.NET AJAX suite if you have purchased the collection and click its Browse all product files button.
+1. Click on **Download Installer and other resources** (the Download link next to the suite if you are a trial user). You need to choose the Telerik UI for ASP.NET AJAX suite if you have purchased the collection and click its Browse all product files button.
 
-1. Download the __Manual installation__ (__ZIP__) file.
+1. Download the **Manual installation** (**ZIP**) file.
 
 1. On the server, create a "Telerik" folder in your "inetpub/wwwroot" folder on the server.
 

deployment/deploying-to-azure.md

@@ -24,7 +24,7 @@ Deploying a project that uses the Telerik UI for ASP.NET AJAX to Windows Azure i
 
 ## Common Issues
 
-__WebResource requests are not returned, which results in missing CSS files and/or scripts.__
+**WebResource requests are not returned, which results in missing CSS files and/or scripts.**
 
 This can often seem like an intermittent problem - i.e. after some deployment attempts the Telerik controls will work, after some - they will not.
 

deployment/protecting-the-telerik-asp.net-ajax-assembly.md

@@ -14,60 +14,60 @@ position: 4
 
 ## 
 
-__Technical guidelines for protecting Telerik UI for ASP.NET AJAX binaries when redistributed with other applications__
+**Technical guidelines for protecting Telerik UI for ASP.NET AJAX binaries when redistributed with other applications**
 
 
 
 
 
 We are providing the following suggestions to protect our IP (Intellectual Property) when redistribute our assemblies as a part of shrink-wrapped software (packaged products).
 
-__Prerequisites__
+**Prerequisites**
 
-Protecting *Telerik UI for ASP.NET Ajax* requires the *Telerik.Web.UI* assembliy to be built from source code (due to modifications applied to the source files). The source code of Telerik UI for ASP.NET AJAX is distributed separately and is bundled with build instructions. Please read the source code building instructions beforehand.
+Protecting *Telerik UI for ASP.NET Ajax* requires the *Telerik.Web.UI* assembly to be built from source code (due to modifications applied to the source files). The source code of Telerik UI for ASP.NET AJAX is distributed separately and is bundled with build instructions. Please read the source code building instructions beforehand.
 
 For brevity this document assumes that the source distribution ZIP file is extracted in C:\TelerikControlsAjaxSource.
 
 
 
-__Instructions__
+**Instructions**
 
-1. Open C:\TelerikControlsAjaxSource\Telerik.Web.UI\Common\AssemblyProtection.cs in a text editor (notepad, Visual Studio etc)
+1. Open *C:\TelerikControlsAjaxSource\Telerik.Web.UI\Common\AssemblyProtection.cs* in a text editor (notepad, Visual Studio etc)
 
 1. Uncomment the following line:
 
 ````C#
-public static void Validate()
-{
- //Uncomment the following line
- //ValidatePassPhrase();
-} 
+public static void Validate()
+{
+ //Uncomment the following line
+ //ValidatePassPhrase();
+} 
 ````
 
 
 
 ````C#
-public static void Validate()
-{
- //Uncomment the following line
- ValidatePassPhrase();
-} 
+public static void Validate()
+{
+ //Uncomment the following line
+ ValidatePassPhrase();
+} 
 ````
 
 
 
-1. Change the value of the *__ApplicationName__* constant to match the name of your application:
+1. Change the value of the ***ApplicationName*** constant to match the name of your application:
 
 ````C#
-//Modify to match your application name
-private const string ApplicationName = "MyApp"; 
+//Modify to match your application name
+private const string ApplicationName = "MyApp"; 
 ````
 
 
 
 ````C#
-//Modify to match your application name
-private const string ApplicationName = "Sample Application Name v2.0 (tm)"; 
+//Modify to match your application name
+private const string ApplicationName = "Sample Application Name v2.0 (tm)"; 
 ````
 
 
@@ -77,14 +77,12 @@ __Instructions__
 1. In your application replace the existing reference to Telerik.Web.UI.dll with the one built from source code.
 
 1. If you run your application now you should see the following error message (“Sample Application Name v2.0 (tm)” will be replaced with the name of your application set in step 3):
->caption 
-
 ![](images/introduction-applicationisnotlicensed.jpg)
 
-1. Add the following code in the Page_Load method of your page codebehind class.
+1. Add the following code in the Page_Load method of your page code-behind class.
 
 ````C#
-Application["Telerik.Web.UI.Key"] = "Sample Application Name v2.0 (tm)";
+Application["Telerik.Web.UI.Key"] = "Sample Application Name v2.0 (tm)";
 ````
 
 

deployment/using-the-global-assembly-cache.md

@@ -12,7 +12,7 @@ position: 1
 
 
 
-This article explains the basics on using the[Global Assembly Cache (GAC)](http://msdn.microsoft.com/en-us/library/yf1d93sz.aspx)with the Telerik Controls.
+This article explains the basics on using the [Global Assembly Cache (GAC)](http://msdn.microsoft.com/en-us/library/yf1d93sz.aspx)with the Telerik Controls.
 
 While this article can be used as a tutorial on working with the GAC and referencing assemblies in your project,	the best source of information is the official MSDN site:
 
@@ -30,7 +30,7 @@ While this article can be used as a tutorial on working with the GAC and referen
 
 The [Telerik UI for ASP.NET AJAX assemblies]({%slug introduction/installation/included-assemblies%}) are standard .NET assemblies, so all generic rules apply to them as well.
 
-What we advise is that you __keep the Telerik.Web.Design.dll assembly in the GAC on your development machine (it is not needed in production)__(our installation wizard will put it there) in order to have access to the design-time mode of the controls, and __reference the other assemblies (Telerik.Web.UI.dll and Telerik.Web.UI.Skins.dll) from the BIN folder__.
+What we advise is that you **keep the Telerik.Web.Design.dll assembly in the GAC on your development machine (it is not needed in production)**(our installation wizard will put it there) in order to have access to the design-time mode of the controls, and **reference the other assemblies (Telerik.Web.UI.dll and Telerik.Web.UI.Skins.dll) from the BIN folder**.
 
 This article contains the following sections:
 
@@ -70,9 +70,9 @@ GAC is the short version of "Global Assembly Cache". It is a common place in the
 
 ## Where is the GAC
 
-Up __until .NET 3.5__ the GAC is located in__C:\Windows\Assembly\__
+Up **until .NET 3.5** the GAC is located in **C:\Windows\Assembly\**
 
-__Since .NET 4.0__ it is in __C:\Windows\Microsoft.Net\Assembly\GAC_MSIL\__and also the shell integration was removed, so you can no longer drag-and-drop an assembly in the folder and have it registered.
+**Since .NET 4.0** it is in **C:\Windows\Microsoft.Net\Assembly\GAC_MSIL\** and also the shell integration was removed, so you can no longer drag-and-drop an assembly in the folder and have it registered.
 
 ## Pros and Cons
 
@@ -100,7 +100,7 @@ And one that can go in either category:
 
 ## Add, Remove and View Assemblies in the GAC
 
-First, you are going to need a tool from the .NET SDK that comes with Visual Studio – [gacutil.exe](http://msdn.microsoft.com/en-us/library/ex0ss12c%28v=VS.100%29.aspx). To run it go to-> All Programs -> Visual Studio <version> -> Visual Studio Tools -> run the [Visual Studio Command Prompt](http://msdn.microsoft.com/en-us/library/ms229859.aspx) (or Developer Command prompt, depending on the VS version you use.
+First, you are going to need a tool from the .NET SDK that comes with Visual Studio – [gacutil.exe](http://msdn.microsoft.com/en-us/library/ex0ss12c%28v=VS.100%29.aspx). To run it go to -> All Programs -> Visual Studio <version> -> Visual Studio Tools -> run the [Visual Studio Command Prompt](http://msdn.microsoft.com/en-us/library/ms229859.aspx) (or Developer Command prompt, depending on the VS version you use.
 
 ### View the Assemblies in the GAC
 
@@ -138,7 +138,7 @@ Here is an example that removes the Q3 2014 Telerik.Web.UI.dll assembly to the G
 
 `gacutil /u Telerik.Web.UI, Version=2014.3.1209.45, Culture=neutral, PublicKeyToken=121fae165ba3d4`
 
-You can read more on the subject in the[How to Uninstall an Assembly from the GAC](http://msdn.microsoft.com/en-us/library/aa559881.aspx) MSDN article.
+You can read more on the subject in the [How to Uninstall an Assembly from the GAC](http://msdn.microsoft.com/en-us/library/aa559881.aspx) MSDN article.
 
 >tip If an assembly has been added to the GAC by an automated installer, to remove it from the GAC, you must first uninstall the program that added it.	The Telerik UI for ASP.NET AJAX installer adds the Telerik.Web.UI.Design.dll assembly to the GAC.
 >
@@ -150,27 +150,27 @@ You can read more on the subject in the[How to Uninstall an Assembly from the GA
 
 ### In a WebSite Type of Project
 
-In a __Web Site type of project__, the __Property Pages__ dialog can show you whether the references are from the GAC:
+In a **Web Site type of project**, the **Property Pages** dialog can show you whether the references are from the GAC:
 >caption Figure 1: GAC references to Telerik assemblies in a WebSite project
 
 ![website gac reference](images/website_gac_reference.png)
 
-You can also see the references in the __web.config__. They will have fully qualified assembly names. For example:
+You can also see the references in the **web.config**. They will have fully qualified assembly names. For example:
 
 ````XML
-<compilation debug="true" targetframework="4.0"> 
-<assemblies> 
-<add assembly="Telerik.Web.UI, Version=2012.3.1016.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4" /> 
-<add assembly="Telerik.Web.UI.Skins, Version=2012.3.1016.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4" /> 
-</assemblies> 
-</compilation>
+<compilation debug="true" targetframework="4.0"> 
+<assemblies> 
+<add assembly="Telerik.Web.UI, Version=2012.3.1016.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4" /> 
+<add assembly="Telerik.Web.UI.Skins, Version=2012.3.1016.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4" /> 
+</assemblies> 
+</compilation>
 ````
 
 
 
 ### In a WebApplication Type of Project
 
-In a __WebApplication type of project__, you have to examinethe __reference Properties__ under the __References__node in the __Project__ tree. You will see how it is not a local copy of the assembly and that the path points to the GAC:
+In a **WebApplication type of project**, you have to examine the **reference Properties** under the **References** node in the **Project** tree. You will see how it is not a local copy of the assembly and that the path points to the GAC:
 >caption Figure 2: GAC references to Telerik assemblies in a WebApplication project
 
 ![webapplication gac reference](images/webapplication_gac_reference.png)
@@ -181,49 +181,43 @@ In a __WebApplication type of project__, you have to examinethe __reference Prop
 
 An alternative to the GUI approach below, you can simply add a few lines to theweb.config, as shown in the [How GAC References Look](#how-gac-references-look) section.
 
-1. Open the __Property Pages__ dialog, go to the__References__ tab and click __Add__:
+1. Open the **Property Pages** dialog, go to the **References** tab and click **Add**:
 >caption Figure 3: Open the Property Pages and add a reference.
-
 ![add-gac-reference-website-1 site property pages](images/add-gac-reference-website-1_site_property_pages.png)
 
 1. Browse to the GAC to select assembly:
 >caption Figure 4: Browse to the GAC and select an assembly to reference.
-
 ![add-gac-reference-website-2 browse to gac](images/add-gac-reference-website-2_browse_to_gac.png)
 
 1. Confirm the reference properties when you make sure they are correct:
 >caption Figure 5: Examine the references and close the Property Pages dialog.
-
 ![add-gac-reference-website-3 site confirm properties](images/add-gac-reference-website-3_site_confirm_properties.png)
 
 ### In a WebApplication Type of Project
 
-1. Open the __Add Reference__ dialog:
+1. Open the **Add Reference** dialog:
 >caption Figure 6: Open the Add Reference dialog.
-
 ![add-gac-reference-webapp-1 app add reference](images/add-gac-reference-webapp-1_app_add_reference.png)
 
 1. Browse to the GAC to select assembly:
 >caption Figure 7: Browse to the GAC and select an assembly to reference.
-
 ![add-gac-reference-webapp-2 browse to gac](images/add-gac-reference-webapp-2_browse_to_gac.png)
 
 1. Confirm the reference properties and you make sure they are correct:
 >caption Figure 8: Examine the references.
-
 ![add-gac-reference-webapp-3 app confirm properties](images/add-gac-reference-webapp-3_app_confirm_properties.png)
 
 ### Troubleshooting GAC References
 
 The first problem you may encounter is that the .NET tab of the Add Reference dialog box in VS will not show custom assemblies you have added to the GAC, you either need a third party plugin for your IDE, or a registry key so that it can know about this third-party assembly. Manually browsing to the desired folder is an easy resolution.
 
-Make sure to always __reference the same versions of all Telerik assemblies__ used in the project.
+Make sure to always **reference the same versions of all Telerik assemblies** used in the project.
 
-If you get the __"Could not load file or assembly…"__ error. It means the reference is typed in wrongly or the assembly is not actually in the GAC of the machine. This can also be caused by wrong version numbers (e.g. Register directives left over in old user controls). You can consider using a *bindingRedirect* element to redirect all old references to the current one you need. This is useful for SharePoint and Sitefinity scenarios.
+If you get the **"Could not load file or assembly…"** error. It means the reference is typed in wrongly or the assembly is not actually in the GAC of the machine. This can also be caused by wrong version numbers (e.g. Register directives left over in old user controls). You can consider using a *bindingRedirect* element to redirect all old references to the current one you need. This is useful for SharePoint and Sitefinity scenarios.
 
-__"CS0433: The type '<RadControl class>' exists in both '<assembly in the GAC>' and '<Temporary ASP.NET Files for the site>"__—this means there is a duplicate reference to our assembly – one that points to the GAC and one that points to a file somewhere else on the machine. To fix this, makes sure the project references are correct and clear the ASP cache.
+**"CS0433: The type `<RadControl class>` exists in both `<assembly in the GAC>` and `<Temporary ASP.NET Files for the site>`"** —this means there is a duplicate reference to our assembly – one that points to the GAC and one that points to a file somewhere else on the machine. To fix this, makes sure the project references are correct and clear the ASP cache.
 
-# See Also
+## See Also
 
  * [MSDN: Global Assembly Cache](http://msdn.microsoft.com/en-us/library/yf1d93sz.aspx)