Empowering development teams to deliver modern-looking solutions in less time requires a periodical revision of Progress Developer Tools offerings. It goes both ways – adding new products to meet evolving business needs and retiring tools that have served their purpose. Investing our efforts in the right direction ensures you get the most up-to-date solutions to build engaging UI and elevate user experience.
We would like to inform you that Progress Telerik UI for ASP.NET AJAX Extension (Visual Studio 2015, 2017) for Progress® Telerik® UI for ASP.NET AJAX is now deprecated. This means that we will no longer be actively maintaining or updating this extension. From now onwards we shift our focus to creating and maintaining extensions specifically designed for Visual Studio 2019 and 2022.
What does this Progress Telerik UI for ASP.NET AJAX Extension (Visual Studio 2015, 2017) deprecation mean for you?
- No further updates or improvements will be released for this specific extension.
- Limited support only will be provided for issues or inquiries related to the deprecated extension.
- Migration to our extensions for Visual Studio 2019 and 2022 is highly recommended.
We appreciate your trust in us and thank you for your support along the way.
If you have questions, don't hesitate to reach out to our support team.
Telerik UI for ASP.NET AJAX Extension for VS 2022
Telerik UI for ASP.NET AJAX Extension for VS 2019
Overview
The Progress® Telerik® Visual Studio Extensions package introduces a new level of developer productivity with a simplified and fast way to develop your Telerik UI Website/WebApplication. The product helps you work smarter with streamlined features and increased control of the Integrated Development Environment (IDE) and minimizes the learning curve for new users. The ASP.NET AJAX Visual Studio Extensions Wizards automatically create, upgrade and configure your Telerik UI projects in seconds, eliminating the need to set any assembly references, handler/module definitions, tag prefixes, etc. manually. Additionally, the Visual Studio Extensions Package includes a set of ready-to-use Visual Studio templates that cover common application scenarios for Progress® Telerik® UI for ASP.NET AJAX.
Key Features (Highlights) of ASP.NET AJAX Visual Studio Extension
- 120+ premium and multi-award winning, lightweight, WCAG/JAWS accessible and user-friendly UI controls built over ASP.NET Web Forms
- Support for all popular browsers, including legacy browsers such as IE9-IE11.
- 3 major releases with 3 service packs per year
- Professional wizards for fast project creation, upgrade and configuration
- Jump start with ability to choose from multiple predefined scenarios
- Detailed documentation, Rich API and customization capabilities plus a demo app with over thousand examples and 7 real-life sample apps
Project Creation and Configuration Wizards
Create New Project in Visual Studio
The Create New Project add-on helps you create in a fast and reliable way a new Telerik ASP.NET Web Forms project (web site and web application) with the Telerik ASP.NET AJAX controls in. It handles and registers automatically the assemblies’ references, web.config modifications and management of additional resources (scripts, skins, assemblies and more). Invoke the Visual Studio Create a new project wizard and select the Telerik Web Forms Application or Site (C# or VB.NET flavors). Give your project a name in the Configure your project Visual Studio option. This will open the Create New Telerik Project wizard where you can pick the desired Telerik project template (Default, Responsive or Web Mail).
More info is available in the documentation.
This Telerik ASP.NET Web Forms Visual Studio Extensions add-on allows you to fine tune the project settings such as: which helper assemblies you’d like to be added to the project, which skin to be applied to the Telerik controls as well as some web.config settings like enabling the CDN and jQuery support.
You can find more details in the documentation.
You can easily convert your standard ASP.NET Web Forms project to a Telerik Web Application one with the help of the Telerik Convert Project wizard in Visual Studio.
To learn more on this feature check out this article.
An important feature that comes with installing the Telerik UI for ASP.NET AJAX Visual Studio Extensions is the Upgrade Project Wizard. It can facilitate the process of upgrading the Telerik AJAX controls to the latest version in your project.
API Analyzer
The purpose of this useful tool is to make your upgrade process easier by comparing the two Telerik ASP.NET AJAX versions from which you update from and to and determining the problematic areas. See more here.
Add Scenario Page Creation
The Add Scenario wizard in Visual Studio aids creating pages with the most common controls and scenarios in the usage of Telerik UI for ASP.NET AJAX.
This useful feature allows you to select which version of Telerik UI to be populated in the Visual Studio Toolbox. For more in-depth overview of the extension, please refer to this documentation article.
Download New Version
With the Telerik ASP.NET AJAX Visual Studio Extensions you can use the New Version Downloader tool, which keeps your projects always up to date. If there is a new version, you will get notified so that you can plan and upgrade your app to it. For more detail, check out here.
Help Resources
a. Learn More about Telerik UI for ASP.NET AJAX Controls
b. Download Free Trial
c. Documentation
d. Online Demos
e. Release History
f. Pricing and upsell options
g. Community Forums
h. Suggest a Feature
Revision notes
2023.1.426
- What's new:
- Separate packages for VS 2015/VS 2017
- Change the default browser when launching API Analyzer
- What's Fixed
- After an upgrade Visual Studio is launched in Admin mode
2023.1.405
- What's New
- Internal improvements and refactoring
2023.1.313
- What's New
- Internal improvements and refactoring
2023.1.113
- What's Fixed
- Upgrade wizard for UI for ASP.NET AJAX does not configure the toolbox with the newly used version
2022.3.1108
- What's New
- Use Telerik web login for VS extensions authentication
2022.3.926
- What's Fixed
- System.IO.FileNotFoundException is thrown in Visual Studio 2015
2022.3.902
- What's Fixed
- Handle wizards' crashes when no product distribution is installed
2022.2.602
- What's Fixed
- Visual Studio gets unresponsive when loading SSDT/SSIS/SSRS projects and Telerik extension(s) are installed
2022.2.429
- What's Fixed
- Release notes link from Newer version notification for LIB leads to the page of Official Releases' notes
- Toolbox Configurator doesn't populate controls
2022.1.111
- What's Fixed
- ShowNotificationsError handled error is sent for missing Telerik.SystemSettings.dll in VS2022 extension
2021.3.1203
- What's Fixed
- Exception is thrown when adding an item template to a project located in solution folder
2021.2.614
- What's Fixed
- FileNotFound exception is thrown when Upgrading/Configuring project with non existing web.config
2021.2.505
- What's New
- Added new document processing assembly Telerik.Documents.Flow.FormatProviders.Doc
- What's Fixed
- Exception is thrown while upgrading a project with a second config file without any appsettings
2021.1.421
- What's Fixed
- Visual Studio 2019 becomes unresponsive when you have Progress Telerik UI for ASP.NET AJAX Extension installed
2021.1.218
- What's New
- Introduce detection of app settings defined in config file different than the default web.config
- What's Fixed
- Configure/Upgrade Wizard changes web.config file name case
- 'Get Latest' does not work in Visual Studio 2012/2013.
- Exclude ItemTemplates assembly from the extensions VSIX
- SystemOverflow exception is thrown when trying to set Visual Studio notifications position and Visual Studio window coordinates are negative
- ASP.NET AJAX wizards upgrade wrong web.config in case several config files exist
- ASP.NET AJAX project templates cannot be ran when web.config appsettings tag contains configSource property
2021.1.108
- What's New
- Update content of VS Marketplace description
- What's Fixed
- FileNotFoundException is thrown when "lib" folder is used in Visual Studio 2017 and Visual Studio 2019
2020.3.1216
- What's New
- Move Telerik user settings into Visual Studio Options dialog
- What's Fixed
- Visual Studio unresponsiveness improvements
2020.3.1117
- What's Fixed
- DirectoryNotFound Exception is thrown when path to ShadowCopy is too long
2020.3.1016
- What's New
- Enable usage tracking of DPL NuGet packages
- What's Fixed
- Telerik.Web.Design assembly is not added by Convert Wizard when no assemblies are selected
2020.3.911
- What's New
- Improve the Unable to launch scenario wizard message
- Add support for Telerik.Documents.Spreadsheet.FormatProviders.Xls and Telerik.Windows.Documents.CMapUtils assemblies in Telerik wizards
2020.2.612
- What's New
- Adapt Notifications to Visual Studio 2019 Telerik menu locations
- What's Fixed
- Remove redundant files form Visual Studio extension package files
2020.2.508
- What's New
- Update icon and preview image in Visual Studio ASP.NET AJAX Extension
- What's Fixed
- FileNotFound exception is thrown when retriving details of an assembly that targets a not restored NuGet package
- ListView.aspx file contains incorrect code when creating Ajax VB Responsive project
2020.1.214
- What's New
- Remove duplicate project template entries in Visual Studio 2019 project wizard list
- Add tags for Visual Studio 2019 project template entries
- Track SpreadSheetStreaming assembly usage
- What's Fixed
- Visual Studio Notifications do not work correctly on monitors with high DPI
- Project type parameter in DPL ComponentUsed metric is always Wpf
2020.1.122
- What's Fixed
- Upgrade wizard sets RenderMode="Lightweight" when updating ASP.NET AJAX Web application
2020.1.115
- What's New
- Update EULAs, Third Party notices and extensions names
- Set RenderMode="Lightweight" in web.config when converting regular ASP.NET Web Forms project to Telerik Web Forms project
- What's Fixed
- Download location is not updated when using Browse button in VS extensions Options wizard
- Project Convert wizard does not add Telerik.Web.Design.dll to the BIN folder
2019.3.1106
- What's Fixed
- System.AggregateException error is thrown when VS extension packages are not initialized
2019.3.1014
- What's Fixed
- Notifications from Telerik Visual Studio extensions do not appear in Visual Studio 2019
- Visual Studio hangs after launching Telerik project from .sln file
- Telerik Visual Studio extensions make RPC (Remote Procedure Call) calls from background threads in AsyncPackage
2019.3.910
- What's Fixed
- Lib folder is not checked-in with Solution when "Integrate with source control" option is selected in Visual Studio Extensions
- Get Latest Version dialog is missing in Visual Studio 2012
- Visual Studio extensions tracking data is not sent for Visual Studio 2012 and Visual Studio 2015
2019.2.614
- What's New
- Improve Visual Studio 2019 template selection
- What's Fixed
- VS extensions throw NullReferenceException while trying to initialize ProductUsedTrackers
- Exception is thrown when New Project Wizard is closed before project creation in VS2019
- Trial message for UI for WPF controls is displayed when opening Scenario wizard
2019.2.503
- What's New
- Updated Newer Online Version notification text
2019.1.404
- What's Fixed
- VSExtensions throw InvalidCastException while creating new project
2019.1.403
- What's New
- Fix "FullPath" property usage in VS extensions
- What's Fixed
- VSExtensions throw NullReferenceException while trying to use TFS integration
2019.1.215
- What's New
- Improve getting user available releases in VS extensions
2019.1.116
- What's New
- Updated Newer Online Version notification text
2019.1.110
- What's New
- Asynchronous VS extensions loading
- Add support for VS 2019 in Visual Studio extensions
- Update company name in VS extensions copyright
- Upgrading Ajax projects removes MVC references and vice versa
2018.4.1121
- What's New
- Visual Studio integration improvements
2018.3.1011
- What's Fixed
- Metrics are always sent when isolated storage xmls are invalid
- Isolated storage files are invalid after removal of old checks
2018.3.907
- What's New
- Update newer online version notifications messages
- Remove warning message in VSX upgrade log when assemblies exist both locally and in GAC
- Add Support Menu Options in VS Extension
- Add snippets installation to Ajax vsix package
- What's Fixed
- UnauthorizedAccessException is thrown when we access %appdata%\Telerik*.xml files
- Microsoft.VisualStudio.Component.TextTemplating component is not added as prerequisite for Kendo and AJAX VSExtensions
- DPL commands in Telerik menu remove all themes referenced by the project
- AJAX wizards do not set HintPath on added/updated references
2018.2.813
- What's Fixed
- An exception is thrown in VS Extensions wizard when identity service cannot be accessed
2018.2.710
2018.2.618
- What's New
- Typos in Outlook-Inspired template of UI for ASP.NET AJAX
- Acquire user consent for collecting data in VS extensions
- What's Fixed
- UI for ASP.NET AJAX VSExtension TypeScript tools detection is missing for VS2017
2018.2.514.1
- What's New
- Update Telerik AD to Telerik EAD in VS extensions
- Update newer online version notifications texts
- Expose DPL in Telerik menu
- Add Conversational UI to VSExtensions
2018.1.215.2
- What's New
- Add Telerik.Windows.Documents.Dlow.FormatProviders.pdf in wizards
- Improve extensions notifications messages
- What's Fixed
- Telerik.Web.Design.dll is not added to the Bin folder of a newly created Telerik AJAX site/app
- VSExtensions throw NullReference exception when trying to handle UnauthorizedAccessException
2018.1.111.4
- What's New
- Update Notifications urls to use secure channel - HTTPS
- What's Fixed
- Telerik name is duplicated in toolbox categories for all products with Toolbox integration
- VS Extensions crash in Visual Studio 2017 due to missing Text Templating component
- Handled XamlParseException is sent when trying to show notifications in VSExtensions
- Extensions notifications do not show up after extension upgrade
- UpdateReferences action throws UnauthorizedAccessException trying to access distribution.xml file
- UnauthorizedAccess exception is shown when user uses notification without write access to %Appdata%\Telerik
- Visual Studio crashes during project upgrade due to AccessViolationException
- UnauthorizedAccessException is shown when the options dialog is used without write access to %Appdata%\Telerik
2017.3.1017.0
- What's New
- Update demos.telerik.com URLs to use HTTPS in VS extensions
- Rename products short names in VS extensions
- Do not deploy Telerik.Web.Design assembly to the GAC
- What's Fixed
- VS Extensions crash on attempt to convert standard web application by adding Telerik Item template
2017.3.906.0
- What's New
- Improve VS extensions UI in custom DPI
- What's Fixed
- VS Extensions UpdateReferences action crash with FileNotFoundException
- Class library project is not detected by Upgrade Wizard
- maxAllowedContentLength value is set to -2048 after project upgrade
- maxAllowedContentLength is not correctly set relative to maxRequestLength
- The setting maxAllowedContentLength is set to invalid value after upgrade.
- Upgrade wizard changes requestLimits maxAllowedContentLength to -1024
- AJAX: returning the default values of Max Request Length and Execution Timeout does not work
2017.2.629.0
- What's New
- Implement monitor DPI and resolution metrics
- Use all release notes URLs in VS Extensions
2017.2.613.0
- What's Fixed
- VS Extensions UpdateReferences action crash with FileNotFoundException
2017.2.501.0
- What's New
- Rebrand Visual Studio extensions
- Update toolbox categories
2017.1.327.0
- What's New
- Add Digital Signature for VSExtensions
- What's Fixed
- Telerik.VSX.Actions.EnsureItemTemplateReferencesAction throws COMException caused by already existing project reference
2017.1.216.0
- What's New
- Integrate Telerik API Analyzer for AJAX VS extensions
- Show unavailable project templates as disabled instead of hiding them when specific distribution is selected
2017.1.113.0
2016.5.1111.0
- What's New
- Added support for Visual Studio 2017 RC
- Dropped support for Visual Studio 2010
2016.4.1021.0
- What's Fixed
- XamlParseException is thrown when notifications are shown
- VS Extensions crash when non-existent drive is entered in backup location path in Upgrade Wizard
2016.3.909.0
- What's New
- Add link to release notes in the new version notification in Visual Studio
- Implement notifications synchronization
- Rebrand VS extensions
- Add Trial notifications in VS extensions
- Prefill credentials in Get Latest Version dialog when user has already logged in
- Improve license notifications schedule
- Rework VS extensions About dialog
- Improve how VS extensions notifications are displayed
- Add product/extension name in latest version acquirer
- Rework VS extensions user settings UI design
- What's Fixed
- Wrong text in VS Extensions Upgrade wizard
- Error message is shown when tracking products in VS extensions
- There is no field validation for Download folder in VSExtensions options
- VSExtensions icons are jagged in the Extensions Manager for Visual Studio 2013 or later
- Telerik.VSX.Shell.VS10 assembly does not have strong name
- System.Windows.Markup.XamlParseException is thrown in VS extensions
- Suggest Trial to Dev update option name in User Settings package is not clear
- VS extensions crash if AJAX main assembly is corrupted
2016.2.712.0
2016.2.603.0
2016.2.428.0
- What's New
- Rework UI design in convert wizard
- Rework UI design in configure wizard
- Rework UI design in toolbox configuration wizard
- Rework UI design in new item template wizard
- Rework UI design in upgrade wizard
- Rework UI design in create new project wizard
- Add link to documentation in VS extensions
- Add "How to" information in toolbox wizard for users that have no admin privileges
- Mark Latest Internal Builds in VS Extensions so that users can distinguish them
- Create Outlook-Inspired project template
- Add Telerik.Documents.SpreadsheetStreaming assembly
- What's Fixed
- In the RadGridAutomaticCrudOperation.aspx file a deprecated CSS value for “cursor” property is deployed
- Responsive project type could not be run when using older distribution than Q1 2015
- Visual Studio crashes if multiple notifications are shown and they fade-out
- Upgrade Wizard does not detect Telerik projects when CopyLocal property is set to false
- Fix key navigation in navigation pane
- Ajax project could not be built after adding Image Uploader item template
2016.1.414.0
- What's Fixed
- VSExtensions crash when using Text Templating in Visual Studio 2015 Update 2
2016.1.111.0
- What's New
- Remove Data Access integration from the New Project wizard
- Add method name in VS extensions error reports
- Add release mismatch metrics in VS extensions
- Add support for Web.Spreadsheet in AJAX VS Extensions
- Add RenderMode=LightWeight tag in the Web.config file for AJAX project
- What's Fixed
- Misleading message is shown in the Upgrade wizard log when using in-project references
- ComponentUsed tracking is not send for WebSite projects
2015.5.1030.0
2015.4.925.0
- What's New
- Added wizard usage tracking in VS extensions
- Added third party EULAs in VS extensions installation folder
- What's Fixed
- VS extensions does not show distribution correctly when distribution path contains "System"
- Create New Telerik Project does not preselect the correct category and template when Reporting is installed
- Save my password option does not work in Get Latest Version dialog
- Httpruntime targetFramework="3.5" is set for project targeting .Net Framework 4.5 on multiple project upgrade
- property value is set to 2.0 when solution explorer is closed
2015.3.622.0
- What's New
- Send ProductUsed metric only once per day and product
- Report product code and Visual Studio version in ProductUsed event
- Add VS templates usage metrics in VS extensions
- What's Fixed
- Using Telerik Configure Wizard from Telerik menu throws an error report when Visual Studio 2010 IDE Solution Explorer is closed
- Adding Telerik item template from Telerik menu throws an error report when Visual Studio 2010 IDE Solution Explorer is closed
- Session Id parameter in callhome events is different for each product
- Upgrade wizard crashes when trying to write upgrade log to not existing location
- VS extensions crash when browsing to the distribution with different target .NET framework than this of the project in VS 2008
2015.2.317.0
- What's Fixed
- VS extensions licensing access token is not refreshed if Visual Studio is running
- License tracking does not work under Visual Studio 2010
2015.1.224.0
- What's New
- Added support for Visual Studio 2015
- Added new project templates
- Automatically select DPL assemblies in New Project and Convert wizards
- Removed RadHttpModule and RadCompression options
- Removed .NET 2.0 support
- What's Fixed
- Upgrade and Convert wizards removes Telerik.Windows.RadUploadHandler reference when Silverlight project is hosted in web project
- Configure and Upgrade wizards remove Telerik.ScriptManager.TelerikCdn and Telerik.StyleSheetManager.TelerikCdn tags from web.config file
2014.6.1124.0
- What's New
- Improved handling of additional assemblies
2014.5.1021.0
- What's New
- Add new snippets in AJAX VS extensions
- Add option for TypeScript definitions in Ajax VS extensions
- What's Fixed
- VS extensions crash on UnsubscribeSaveEvents
- There is no verification if there is an assembly distribution when adding Item Template to a Telerik project with invalid reference
- VSExtensions crash when adding an Item template to regular application and there is no controls distribution found
2014.4.918.0
- What's New
- Add support for .Net Framework 4.5.2
- What's Fixed
- Creating new project with latest VS extensions crashes when the project references solution distribution created with previous version of the extensions
- There is no verification if there is an assembly distribution when adding Item Template to a Telerik project with invalid reference
- Item templates cannot be added to Telerik project when "Add distribution to solution" option is checked and distribution has additional paths
- Adding Item Template to a Telerik WebSite project after the distribution was moved crashes the VSExtensions
- Upgrade wizard fails to upgrade Telerik project
2014.3.820.0
- What's New
- Add support for Document Processing Library in Ajax VS extensions
- Add warning message in Upgrade Wizard
- What's Fixed
- VS extensions crash after opening the Upgrade wizard when the solution file is selected in the solution explorer
- Spell mistake in the VSExtensions Error report dialog
2014.2.707.0
- What's Fixed
- VS extensions crash with System.InvalidCastException when closing solution in Visual Studio
2014.1.616.0
- What's New
- Update AJAX "Default Advanced Form Template" item template
2014.1.514.0
- What's Fixed
- Wrong UI colors in VSExtensions when using Visual Studio standard themes
- Cannot scroll with mouse wheel in the Skin Packs section of the Project Configuration wizard
- Hardly visible assembly names when standard Dark theme is used
2014.1.318.0
- What's Fixed
- Upgrade wizard fails if there is no .sln file created
- VS extensions crash when adding Telerik scenario inside a project folder
- Regular web application project could not be converted to Telerik one by adding Telerik Scenario
- Hotfix distribution on a custom location could not be added in the Distribution list when converting regular web application for .Net Framework 4.5.1
2013.3.1316.0
- What's New
- Updated wizards and icons design
- Updated product name
2013.3.1031.0
- What's Fixed
- Fixed: Telerik compatibility issue
2013.3.1022.0
- What's New
- Telerik credentials saved on shared location for all Telerik products
- What's Fixed
- Visual Studio 2013 hangs when opening solution containing Windows Store C++ project under Windows 8.0
2013.3.926.0
- What's New
- Support for Visual Studio 2013
- Support for .Net 4.5.1
- What's Fixed
- Fixed: Inconsistency between the position of the 'Add referenced assemblies to solution' checkbox in the wizards
- Fixed: Help tool tip content has a repeating text
2013.2.611.0
- What's New
- Added snippets for RadDropDownList, RadDropDownTree and RadSearchBox controls
- Improve source control integration directory structure.
2013.1.222.0
- What's New
- Improve project setup in regard to source control integration
2012.3.1212.0
- What's New
- Resolve Telerik VSExtensons compatibility problems
- Update of User Settings package version
2012.3.1016.0
- What's New
- Telerik RadControls for ASP.NET AJAX Q3 2012 release compatibility update
2012.2.913.0
- What's New
- Telerik WebUI VSExtensions UI Refresh
- Visual Studio 2012 UX implementation
2012.2.815.0
- What's New
- Telerik RadControls for ASP.NET AJAX Q2 2012 RTM refresh release compatibility update
2012.2.724.0
- What's New
- Telerik RadControls for ASP.NET AJAX Q2 2012 SP1 release compatibility update
2012.2.709.0
- What's Fixed
- Optimized solution load times
2012.2.606.0
- What's Fixed
- Configure wizard fails to launch if there is a broken reference
- In project design dlls' version is not updated after upgrade
- Upgrade Wizard fails to remove in-proj reference files when they are resolved to project bin folder
- AJAX Main menu and context menu are available for MVC4 projects
- LINQ shortcut is missing on "Choose Data Source type" page in Scenario Wizard for VS11
2012.1.419.0
- What's New
- Telerik RadControls for ASP.NET AJAX Q1 2012 SP1 release compatibility update
2012.1.320.0
- What's New
- Improved: Inconsistency in the toolbox groups naming
- What's Fixed
- Fixed: AJAX Upgrade Wizard breaks Sitefinity Projects
- Fixed: Scenario wizard fails when attempt to add a scenario through the Add New Item context menu in VS2012
- Fixed: Upgrade Wizard fails when there are missing tags in the web.config file
2012.1.214.0
- What's New
- Telerik RadControls for ASP.NET AJAX Q1 2012 release compatibility update
2011.3.1305.0
- What's Fixed
- Fixed: .NET version is not displayed in Toolbox groups names after Toolbox configurator is used
- Fixed: Scenario wizard fails when attempt to add a scenario through the Add New Item context menu
- Fixed: No skins available when trying to add scenario to nontelerik project
- Fixed: RadToolTip scenarios use Telerik skin by default
- Fixed: Upgrade Wizard issue: Wrong target framework version for web.config
2011.3.1219.0
- What's Fixed
- Fixed: Scenario wizard fails when attempt to add a scenario through the Add New Item context menu
- Fixed: No skins available when trying to add scenario to nontelerik project
2011.3.1125.0
- What's Fixed
- Fixed: The VSExtensions now detect if .NET 3.5 OpenAccess project templates are available so that the projects created are consistent.
- Fixed: The Upgrade Wizard now adds a reference to the Telerik.Web.UI.Skins assembly to maintain the previously used themes in the application.
2011.3.1116.0
- What's new
- Added: Improve the Upgrade Wizard in regards to changing the target fremework
- Added: Make Visual Studio Extensions download folder configurable
- Added: Open Access integration in VS2010 project templates
- Added: Upgrade Wizard should upgrade Scripts and Skins when applicable
- What's Fixed
- Fixed: Issues with parallel Visual Studio Extensions versions installed
- Fixed: Machine text size > 100% garbles the wizard UI
- Fixed: Wrong encoding in VS Template files
2011.2.915.0
- What's Fixed
- Fixed: Fully qualified assembly reference not removed from web.config in .NET 4.0
2011.2.831.0
- What's New
- Added: Added new scenarios for RadControls for ASP.NET AJAX
- What's Fixed
- Fixed: Upgrade wizard sets wrong tagPrefix in web.config
- Fixed: Minor improvements in the codebase, related to Upgrade Wizard issues with a WebSite in the Telerik WebUI VSExtensions.
2011.2.719.0
- What's Fixed
- Fixed: Upgrade wizard issues
2011.2.712.0
- What's New
- Improved: Downloading Telerik AJAX controls updates through VS Extensions (asynchronously)
- Improved: Get Latest Version wizard UI
- Improved: ToolBox upgrade
- Added: Solution-wide upgrade
- Added: Toolbox items grouping
- Added: Support for the new Telerik.Web.UI.Skins assembly in RadControls for ASP.NET AJAX
- What's Fixed
- Fixed: Toolbox configuration failure in VS2008 under UAC
- Fixed: Installation failure during resource deployment
- Fixed: VS2008 doesn't restart after toolbox configuration under UAC
- Fixed: Incorrect upgrade log because of wrong API
- Fixed: Browsed custom distributions not persisted
2011.1.519.0
- What's Fixed
- Fixed: Installer label glitch
- Fixed: item templates issue in cleaned projects
- Fixed: RadEditor Scenario is missing
- Fixed: RadGrid Scenario does not compile
- Fixed: RadScheduler control scenario throws error
2011.1.421.0
- What's Fixed
- Fixed: Incorrect reference path added when running the UpgradeWizard in VS2010
2011.1.315.0
- What's New
- Improved: Project Management wizards can not finish when no assemblies are selected
- Added: AJAX Item Templates to Telerik enable projects
- Added: Telerik Scenario Item Template for Visual Studio WebSite projects
- What's Fixed
- Fixed: All VS template files are saved in the machine's default encoding instead in Unicode
- Fixed: Browsed custom distributions not persisted
- Fixed: Upgrade log shows invalid warnings when upgrading project with GAC references with other GAC references
- Fixed: Reference not updated if the referenced assembly is contained in the project
- Fixed: VS Extensions' context menu is displayed for ASP.NET Special folders
- Fixed: VS Extensions wrong behaviour when delete Bin folder
2010.3.1317.0
- What's New
- Improved: Toolbox Configurator UI
- What's Fixed
- Fixed: Design-time issues (InvalidCastException) when having parallel installs
2010.3.1109.0
- What's New
- Added: A new ToolBox Configuration utility to keep the Toolbox and the project references in sync
- Added: A common Options dialog to manage notifications
- Added: Scenario creation can now be triggered through the New Item dialog of Visual Studio
- Added: Latest internal builds can be downloaded through the VSExtensions (activated through the Options dialog)
- Added: New controls scenarios for RadEditor, RadScheduler and RadWindow
- What's Fixed
- Fixed: UpgradeLog notes assembly reference not updated while the reference is actually updated
- Fixed: Project wizard crash
- Fixed: Starting the Upgrade Wizard throws an error when tagPrefix is missing from web.config
- Fixed: Saving a class in a WebSite now works normally (took too much time when there are lots of classes in the App_Code folder)
- Fixed: Web.Config modules node duplicated when an attribute exists
- Fixed: Upgrade Wizard adds a duplicate ScriptHandler registration to the Web.Config
- Fixed: Operation could not be completed" error when attempting to debug a newly created Telerik project
