NetAdvantage for ASP.NET Product Changes in 2011 Volume 2

Infragistics has been developing ASP.NET controls since the ASP.NET framework was released during early 2000s. Since then, we have provided the toolset that have helped web developers take advantage of the Microsoft’s web platform, combined with the RAD environment & tooling for Visual Studio to build rich, interactive web applications. A lot has changed since then, ASP.NET framework has undergone 5 iterations, IE is no longer the dominant browser in the public space, Visual Studio has gone through 4 iterations, and from the client technology front there have been numerous updates on HTML standards, CSS, AJAX frameworks. Today, the web talks are all about JavaScript, HTML5, CSS3 and the modern browsers including Mobile Web.

These are a lot of changes, almost all the web elements from browsers, to frameworks to the client technologies have gone through iterations, the toolset that Infragistics started developing almost a decade ago was faced with some major challenges to keep up with all of these updates. The controls were not designed in a way that it could accommodate all these changes as they were happening and the code was becoming fragile as we continue to make tweaks to expand our reach as much as we could. We did not update the classic controls to support Web Kit browsers like Safari & Chrome because it would’ve required major rewriting of our rendering engine, which would pretty much mean breaking a lot of existing applications. Hence, we decided to build a new framework based on latest standard with performance in mind and modern browser support, named Aikido. We started developing the framework in late 2007 and since then any new controls we’ve shipped has been based on this new Framework.

We started addressing the sunset plans for some of the ASP.NET controls with a blog that I posted early last year. We do understand that this affects many of you, and we will continue to provide support as much as we can in this area. Input and feedback have been really helpful in making sure we make this transition and change as easy as possible for customers who plan to upgrade to our lasted framework stack. Here are some of the commonly questions asked:

What controls are retiring?

After going through the list of all the ASP.NET controls, the following controls were flagged as classic due to the fact that the code base was old and we were not able to expand browser reach on those.

  • WebGrid
  • WebCombo
  • WebDateChooser
  • WebListBar
  • WebCalendar
  • WebToolbar
  • UltraWebTab
  • WebDataInput
    • WebTextEdit
    • WebMaskEdit
    • WebNumericEdit
    • WebDateTimeEdit
    • WebPercentEdit
    • WebCurrencyEdit
  • WebMenu
  • WebTree
  • WARP Panel
  • WebPanel
  • WebNavBar
  • WebWeekView
  • WebGridExcelExporter
  • WebGridDocumentExporter

What is the sunset policy?

The details of the sunset policy & timeframe have been posted on my blog. The controls listed above are no longer part of the product starting 2011 Volume 2 release. These controls are going to be maintained until June of 2012. Developer support on these controls will be available until Q1 of 2014. Since 2010 Volume 1, these controls were taken out of the Visual Studio toolbox, if you need to locate them in prior releases, refer to this help article.

What options do I have?

You don’t have to upgrade if you don’t need to. The controls support the latest versions of Firefox and IE, so if these two are your primary browser targets, then you continue to maintain your existing applications. If you are looking at upgrading application framework over to ASP.NET MVC or are planning to do pure client-side UI development using JavaScript or jQuery, then check out our NetAdvantage for jQuery product, it is meant to cater to such type of web development needs.

On the other hand, if you want to continue to develop on ASP.NET Web Forms and have a need to take your application to Web Kit browsers or take advantage of the Aikido architecture like light weighted ness, and more standard compliance controls, then you’d have to replace the old control with the new one, and wire up the client and server events and functionality accordingly. Here are the one on one replacement for the controls that we are retiring:

 

Classic ASP.NET Control

New Aikido-Based Controls/Replacement

WebGrid

WebDataGrid , WebHierarchicalDataGrid

WebCombo

WebDropDown

WebDateChooser

WebDatePicker

WebListBar

WebExplorerBar

WebCalendar

WebMonthCalendar

WebToolbar

WebDataMenu

UltraWebTab

WebTab

WebTextEdit

WebTextEditor

WebMaskEdit

WebMaskEditor

WebNumericEdit

WebNumericEditor

WebDateTimeEdit

WebDateTimeEditor

WebPercentEdit

WebPercentEditor

WebCurrencyEdit

WebCurrencyEditor

WebMenu

WebDataMenu

WebTree

WebDataTree

WARP Panel

MS Update Panel

WebPanel

WebExplorerBar

WebNavBar

Custom Pager Templates with Aikido Grids

WebWeekView

Old UI, No longer supported in MS Outlook

WebGridExcelExporter

WebExcelExporter

WebGridDocumentExporter

WebDocumentExporter

I am in the middle of migrating over to the new toolset, how can I use both Classic & New Controls?

You can continue to use both the controls if you are on 2011 Volume 1 or earlier. Starting 2011 Volume 2, the classic controls are no longer going to be part of the product. Hence, in order to continue to maintain your applications that use classic controls, we have hosted “Version-Less” assemblies of them. It may require manual upgrade of your projects, but will allow you to continue to use classic controls until you are fully migrated over to the new toolset. You can download the version-less assemblies from the links below.

If you are on CLR 4 you need only assemblies for CLR 4

If you are on CLR 3.5, you'll need assemblies for CLR 3.5 (2011 Volume 1) and assemblies for CLR 3.5 (2011 Volume 2)

You will find an upgrade guide in the zip which contains instructions on how to apply these assemblies to your projects.

Where can I find help migrating to new controls?

Based on the feedback we’ve gotten so far, most of the customers find the grid control replacement to play a major role in the upgrade since it has the most code written around it, rest of the controls are fairly easy to move up. We have created a cheat sheet to help out understand the features and functionality of the new grid and how to configure them.

http://community.infragistics.com/blogs/craig_shoemaker/archive/2011/07/11/introducing-the-webdatagrid-webhierarchicaldatagrid-cheat-sheet.aspx

We’ve record a bunch of videos on the new grids and have posted it at our community site. http://community.infragistics.com/aspnet/media/default.aspx?tags=webdatagrid&Sort=Rating&PageIndex=1

Does the new grid support all the features of the old grid?

One of the things we’ve worked on side-by-side during the sunset planning is maintaining a feature parity matrix. This allows us to have the new grid be compatible to the most commonly used features available as the old one before we retired it. After you go through the list, you will find that the new grids have some features that the classic UltraWebGrid was never able to support.

 

Feature

UltraWebGrid

WebDataGrid

WebHierarchicalDataGrid

Hierarchy

yes

NA

yes

Editing

yes

yes

yes

AJAX

yes

yes

yes

--Load On Demand

yes

yes

yes

----Manual

yes

yes

yes

----Automatic

yes

yes

yes

--AJAX Events

yes

yes

yes

--Virtual Scrolling

yes

yes

no

Templating

yes

yes

yes

--Column Template

yes

yes

yes

--Header Template

yes

yes

yes

--Footer Template

yes

yes

yes

--Empty Template

no

yes

yes

--Error Template

no

yes

yes

--Instantiating at Runtime

yes

yes

yes

--Access Template Controls

yes

yes

yes

--Band Templates

no

no

no

Bound Mode

yes

yes

yes

--DataSet

yes

yes

yes

----DataTable

yes

yes

yes

--IEnumerable

yes

yes

yes

--Self Related tables

no

NA

yes

--DomainDataSource

no

yes

yes

--AccessDataSource

yes

yes

yes

--SqlDataSource

yes

yes

yes

--ObjectDataSource

yes

yes

yes

--LinqDataSource

yes

yes

yes

--XmlDataSource

yes

NA

yes

--HierarchicalDataSource

yes

NA

yes

Unbound Mode

yes

yes

yes

Client Side Functionality

yes

yes

yes

--Adding Rows/Events

yes

yes

yes

--Editing Rows/Events

yes

yes

yes

--Deleting Rows/Events

yes

yes

yes

--Cell/Row/Column Selection

yes

yes

yes

--Keyboard Events

yes

yes

yes

--Mouse Events

yes

yes

yes

--Dynamic Styling

yes

yes

yes

--Cancel Actions

yes

yes

yes

Validation Support

yes

yes

yes

Hidden Columns

yes

yes

yes

Unbound Columns

yes

yes

yes

Merged Cells

yes

CTP

CTP

MultiColumn Headers

yes

Yes

yes

Copy and Paste

yes

Yes

yes

Keyboard Navigation

yes

yes

yes

508 Compliance

yes

yes

yes

Export to Excel

yes

yes

yes

Export to PDF

yes

yes

yes

Paging

yes

yes

yes

--Custom Paging

yes

yes

yes

--Child Band Paging

no

NA

yes

Filtering

yes

yes

yes

Summary

yes

yes

yes

Client side data binding

no

yes

no

Pinned Columns left

yes

yes

no

--Pinned Columns right

no

yes

no

Column Resizing

yes

yes

yes

Column Moving

yes

yes

yes

Tooltips

yes

yes

yes

Sorting

yes

yes

yes

Selection

yes

yes

yes

Activation

yes

yes

yes

Styling

yes

yes

yes

--Css

yes

yes

yes

--AppStyling

yes

yes

yes

--Presets

yes

no

no

Internet Explorer

yes

yes

yes

Firefox

yes

yes

yes

Safari

no

yes

yes

Chrome

no

yes

yes

CRUD

yes

yes

yes

--Auto

yes

yes

yes

--Manual

yes

yes

yes

Switching Data Sources Dynamically

yes

yes

yes

Row Selector

yes

yes

yes

Custom Schema

yes

yes

yes

Row numbering

yes

yes

yes

CalcManager support

yes

no

no

Stationary header/footer

yes

yes

yes

Null text

yes

yes

yes

Saving/loading client profile (layout)

no

yes

yes

Multi-row summaries

no

yes

yes

Ajax (loading) indicator

yes

yes

yes

What is the future of ASP.NET toolset?
We are fully committed to our ASP.NET product and the future of web technologies. We want to continue helping you be even more successful using the Infragistics ASP.NET tools.  This change allows us to focus exclusively on the new, modern Aikido based toolset for Web Forms developers and also our latest jQuery/HTML5 based toolset released under NetAdvantage for jQuery. We will continue to innovate as well as maintaining our market leading data grid rendering performance. As we build out new controls which target modern, RIA scenarios, we will also continue to build more of the rich, high performing line of business controls which target modern browsers and enterprise applications. 

Lastly, I just wanted to let you know that this decision was not an easy one for us, but something we have to do given the market trends and needs. If you have any questions or feedback, feel free to reach out to me at murtazaa@infragistics.com


Comments  (28 )

nickhoare
on Fri, Nov 18 2011 10:16 AM

Sorry but what does "CTP" mean against Merged Cells?

Would it be possible to have some sort of guide to converting an application to using versionless assemblies and how to merge in classic controls with newer versions?

[Infragistics] Murtaza Abdeali
on Fri, Nov 18 2011 11:18 AM

CTP just means that it is a Commuity Technology Preview. We were not able to fully test it in 2011 Volume 2, it will be shipped in 2012 Volume 1.

There is an upgrade guide in the zip download that has instructions on how to use versionless assemblies.

Arshi
on Fri, Feb 10 2012 12:11 PM

you said that the Classic .net controls support the latest versions of Firefox and IE,

So why WebNavBar doesn't work with the latest versions of browsers IE and Firefox.

Arshi
on Fri, Feb 10 2012 12:14 PM

If classics Asp.net Controls work with latest browsers so why WebNavBar doesn't work with the latest version of IE and Firefox.

[Infragistics] Murtaza Abdeali
on Thu, Feb 16 2012 9:28 PM

@Arshi - You have to be on 2011 Volume 1 or above for the classic controls to support latest version of IE & Firefox.

vkmudigonda
on Mon, Feb 27 2012 4:45 AM

am using SplitterPane in my Web application, and it is working in IE7 & IE8, but when i check in IE 9, the splitter pane is not resizing as expected,

am using NetAdvantage Ver 11.1 version, is there any compatability issues with IE 9?

usiddiqi
on Tue, Mar 27 2012 10:44 AM

Hello,

Is there a migration guide which could help in migrating the UltraWebgrid to WebDataGrid, I mean side by side reference of properties and method

jonnydock
on Wed, May 16 2012 5:11 PM

Can you also create a Cheat Sheet for converting from UltraWebToolbar to WebDataMenu?  Please?

jonnydock
on Thu, May 17 2012 10:58 AM

Also a feature parity matrix for WebDataMenu would be really helpful.

svaccount
on Tue, Jul 24 2012 6:05 PM

Your grid support features show the WebDataGrid and WebHierarchicalDataGrid as supporting Unbound Mode.  It is my understanding that this feature has yet to be available on either of these grids and that includes up to version 12.1.  

Anton Pridanov
on Fri, Aug 3 2012 2:49 AM

Can we update our project if it on CLR 2?

1844event
on Thu, Aug 23 2012 4:39 PM

I want to migrate from 10.3 to 2012.1,

guide, steps?

Oystein
on Wed, Sep 26 2012 2:58 PM

What about going from 2011.1 to 2012.1. What do I do with my classic controls, and do I need version less assemblies for my non-classic controls? What is the practical impact of this? When I am done upgrading my pages containing classic controls, do I then just run the upgrade tool to make the whole site use version bound assemblies?

"Make sure for all the non-classic controls that you are using, you copy the version-less assemblies for those controls to your applications bin folder as well. You need to use version-less assemblies for both the controls if you want to you classic and non-classic controls together in an application. "

autharch
on Sun, Oct 28 2012 3:06 PM

I second Anton Pridanov's question:

Can we update our project if it on CLR 2?

acms
on Sun, Apr 7 2013 9:49 PM

I am also in the process of trying to run the latest Version Free 12.2 .dlls under a CLR 3.5 only to find they are not produced. This is not acceptable given I do not have control over our live environments CLR installations. Why not offer all CLR versions in your installations?

Alex
on Fri, Apr 19 2013 4:30 PM

Hi

I’m looking for versión-less assemblies for the Net Advantage controls v12.2 compiled specifically against the .net framework v4.0

According to this post (see link below) from Mr Jason Beres, In the 12.2 release, there should be version-less assemblies for ASP.NET controls for the following CLR’s:

   CLR 3.5

   CLR 4.0

   CLR 4.5

www.infragistics.com/.../updated-support-for-clr-versions-and-visual-studio-versions.aspx

But when I looked on the Net Advantage v12.2 installation, there is only one folder for version-free assemblies which seems to be the ones compiled against CLR 4.5, also this post seems to confirm that... www.infragistics.com/.../380165.aspx

This is kind of confusing, so do you know where/how can I get a copy of those v12.2 version-free dlls compiled with CLR 4.0?

Thanks in advance

gernblandston
on Wed, Jul 24 2013 11:06 AM

Hello,  we are currently running on version 10.3.  We have issues with many of the controls when users are on IE9 so I purchased NetAdvantage v12.2 (I was not aware that the controls would be gone).  So, should I have purchased a different version?  What version will work with IE9 that won't force us to change everything over?

Thanks

inteq1365
on Tue, Aug 27 2013 1:40 AM

We are using IG 11.1 (Classic Controls). Does IG11.1 works in IE10.0 (Full Mode, NOT classic mode) ?

gouxinya@hotmail.com
on Fri, Oct 25 2013 12:57 AM

How can i upgrade to APP.NET 13.1  from 7.3, can you give me a step by step guide? I serach all your site and can't find this  guide.

Subhash Sharma
on Fri, Nov 1 2013 11:45 AM

Hi,

I am using(visual studiao 3.5)) infragistic web controls like UltraWebGrid and some others and using Infragistic35.web.v10.3.dll , Infragistic35.webui.ultrawebgrid.v10.3.dll. On ie9 and ie10 some problems like on sorting grid value is cleared and some other infragistic functionality not working.Is any other dll we need to use for ie9 and ie10.

Please suggest.

Thanks

brusckowski
on Tue, Jan 21 2014 2:42 PM

Why are controls like 'UltraWebTree' and 'UltraWebMenu' not in this post? We have been using this blog post as 'the' list of the controls to be upgraded in our effort to upgrade from v9.x to v2011.1 to Aikido. We are running into surprises where we discover controls to be upgraded which are not listed here. Is there a more exhaustive and official list of legacy controls not supported in Aikido?

Mikko Ray Victoria
on Sun, May 18 2014 10:06 PM

i want to migrate 2008 volume 3 to 2014.1 please help thanks

mardoc
on Fri, Jun 27 2014 6:11 PM

The download links to version free zip files on this page no longer work.   Can someone at Infragistics Fix them?

Subhash Sharma
on Thu, Jul 3 2014 4:58 AM

One question regarding 14.1 version of infragistics..  its supported to Visual studio 3.5(2008).

Subhash Sharma
on Thu, Jul 3 2014 4:59 AM

One question regarding 14.1 version of infragistics..  its supported to Visual studio 3.5(2008).

Subhash Sharma
on Tue, Aug 12 2014 7:46 AM

I have installed the Trial version of 14.1 dll. When i regiter the dll into my application its give me bug i.e. 'expected' . so please suggest how we can register the following?

<%@ Register Assembly="Infragistics4.Web.v14.1" Namespace="Infragistics4.Web.v14.1" TagPrefix="igtbl" %>

cheap products to sell
on Wed, Oct 29 2014 5:58 PM

NetAdvantage for ASP.NET Product Changes in 2011 Volume 2 - Program Office - Infragistics.com Blog

cloucas
on Thu, Nov 20 2014 3:28 AM

We have an application using 2011.1 (and some 2010.3); Is there a guide to move from UltraWebToolBar to WebMenu?