RadAjax for ASP.NET vs. RadAjax
Just like any other product in the new RadControls for ASP.NET AJAX, RadAjax will be the successor of RadAjax for ASP.NET. The new edition consists of the same controls
(RadAjaxManager, RadAjaxPanel, and RadAjaxLoadingPanel) however is implemented according to the new technology. The major characteristics of RadAjax are the following:
- Built on top of Microsoft ASP.NET AJAX, using its programming model
- Uses the Microsoft ASP.NET AJAX engine, not the Telerik proprietary AJAX engine
- Supports only .NET 2.0 and later, while the current RadAjax supports 1.x as well
- Will include new features and performance optimizations, made possible by the underlying Microsoft ASP.NET AJAX framework
- Backwards compatible with RadAjax for ASP.NET (requires minor changes)
- Seamlessly interoperates with all other RadControls for ASP.NET
Backwards compatibility
A top goal in the development of RadAjax was to maintain backwards compatibility. This was an extremely difficult task, yet we are happy to announce that our efforts were
successful. As a result, RadAjax for ASP.NET and RadAjax are completely interchangeable on their main features.
RadAjax can update:
- all controls from RadControls for ASP.NET
- all controls from RadControls
- all standard ASP.NET controls and most 3rd party controls
Similarly, the RadAjax for ASP.NET can update the same types of controls:
- all controls from RadControls for ASP.NET
- all controls from RadControls
- all standard ASP.NET controls and most 3rd party controls
The syntax, controls names, etc. of the new RadAjax is identical to the one of RadAjax for ASP.NET, just the namespace is different. This makes the process of migration (read
below whether you should migrate at all) becomes more or less a matter of tag-name global replace.
If you consider migration of existing projects to the new RadAjax you need to perform 3 easy steps:
- Install Microsoft ASP.NET AJAX if you haven’t already done so and make the required web.config modifications
- Add the RadAjax registration directive (or just drag-and-drop the control from Visual Studio toolbox onto your
- webform)
- Global replace the old tag names (e.g. rada:RadAjaxManager) with the new tag names (e.g. telerik:RadAjaxManager)
This is all you have to do – no other modifications or “migration” of your code is necessary. You don’t even have to remove RadAjax for ASP.NET from your project if you don’t
want to, as it will do no harm. The above steps are described in details in the RadControls documentation.
What is the future of RadAjax for ASP.NET?
As explained before, the release of RadControls for ASP.NET AJAX will not affect Telerik’s support for the existing RadControls for ASP.NET. Although new controls will be only
added to , all existing controls will continue to be enhanced with new features throughout 2007. It be noted that the new releases of the classic ASP.NET controls will not be
mirror versions of their counterparts, as there are features which will be very hard or impossible to implement due to the underlying architectural differences in the two
suites.
In 2008, RadControls for ASP.NET AJAX will be officially launched and existing RadControls will only receive bug fixes and minor enhancements. The products will be fully
supported, though, through at least 2010, after which only “extended support” for the RadControls for ASP.NET will be offered.
In many cases customers do not have to migrate existing applications, since the current controls are pretty much feature complete, stable, and work fine. This is particularly
valid for RadAjax.
We would like to note that we are open to changes based on the feedback we get from the community. Our #1 goal is to serve you well and we will act according to the needs of
the greater part of the community.
Do I have to migrate RadAjax to RadAjax in my old applications?
For most customers with existing application the answer is “No”, because:
- RadAjax for ASP.NET is stable and feature complete.
- It will continue to receive updates and bug-fixes.
- The support team will continue to answer tickets related to the current RadControls suite, after is officially released in early 2008.
- The two suites can be used together, or in other words, you can add new controls available only in the suite to existing applications, without having to change/migrate
anything else.
- RadAjax for ASP.NET can update both the current and the new controls. As a result you don’t have to migrate RadAjax if you just need to add a new control to your
application.
- If you have a .NET 1.x application, you need to stick with the current RadAjax for ASP.NET, since only work on .NET 2.0.
The migration to RadAjax can be gradual and you can also use both current and new RadAjax in the same application even on the same page. They can coexist without any
problems
What shall I use for new applications?
If you are building new applications, we suggest that you start using the new because:
- It will be introducing new features and optimizations, made possible by the underlying ASP.NET AJAX framework
- It can interoperate with the current RadControls for ASP.NET, which do not yet have counterparts
- It is provided with a “Go live” license and will be fully supported, while it is in Beta.
Although backwards compatibility issues are possible, they are very unlikely. Yet we suggest that you spend enough time experimenting and field-testing the new controls before
jumping in all-out production implementations.