Major functionality addition to ASP.NET 1.1 application

Hello,

We have an existing ASP.NET 1.1 application. The client requires that application provide lot of new functionalities. The existing functionality has to be enhanced and different new functionality is to be added.

Please advise :
1. Should we continue with ASP.NET 1.1 or migrate existing code to ASP.NET 3.5 ? What will be disadvantage of continuing with ASP.NET 1.1 ?

2. What steps/modifications/considerations to be taken in moving 1.1 code to 3.5 ? What things to look out for ?

3. If application is moved to 3.5, should CUSTOM Datagrid paging be replaced with ListView and DataPager Controls OR Gridview paging ? (Datagrid is depcrecated in ASP.NET 3.5)

Thank You.

Re: Major functionality addition to ASP.NET 1.1 application

Hi,

In my opinion, you should move to ASP.NET 3.5. You will need to use automatic conversion by VS, and then also do manual changes because that conversion is not 100% correct. It might take some time but the efforts are worth because:

1. You can leverage masterpages (MP), which will make your design consistent and easy to change. MP saves a lot of time.

2. You can leverage MS AJAX, ASP.NET 3.5 has inbuilt AJAX and those control will make your app more responsive.

3. ASP.NET 2.0 and above is slightly faster than 1.1. Also there are a lot of better new controls as well as new concepts like partial classes etc.

4. Better localization support.

There are many other reasons why you should migrate to 3.5, so better do it if you can.

You can use Listview and Datapager, but if data is large, its better to use SQL Server 2005 based paging, or do paging in the database you are using. Transfer only paged data instead of all resultset each time.

Hope this helps,

Vivek

Should we migrate from ASP.NET 1.1 to ASP.NET 3.5

Hello,

Please advise :
1. Should we continue with ASP.NET 1.1 or migrate existing code to ASP.NET 3.5 ? What will be the disadvantages of continuing with ASP.NET 1.1 ?

When MS ASP.NET 1.1 support ends, will it create problem ?

2. What steps/modifications/considerations to be taken in moving 1.1 code to 3.5 ? What things to look out for ?

3. If application is moved to 3.5, should Datagrid CUSTOM paging be replaced with ListView and DataPager Controls OR Gridview paging ? (Datagrid is depcrecated in ASP.NET 3.5)

Current paging uses DB stored procedure with Datagrid.

Thank You.

Re: Major functionality addition to ASP.NET 1.1 application

In ASP.NET 1.1 application, we use custom datagrid paging with Db stored procedure.

Can we use same Db SP and replace datagrid (as it is deprecated) ?

What are disadvantages of migrating ?

What things to consider while migrating ?

Re: Should we migrate from ASP.NET 1.1 to ASP.NET 3.5

Well, ti depends what kind of new functionality will be new from your existent application. I recommend focus is your client requirements and if your actual application doesn't meet the requirements you could move to ASP.NET 2.0 to include MasterPages, User Profile, skins, using Generics, SQL and Object Datasource and some other new features from 1.1 to 2.0 (2.0 have been an excellent update of the Framework). If you need to include newest features in 3.5 like LINQ, Lambda Expression, ASP.NET Ajax integrated you might to upgrade to 3.5. If you only want to change the version of Viisual Studio to take advantage of CSS new Features and ASPX designer you still can have 1.1 (VS 2008 has compatibility with 1.1, 2.0, 3.0 and 3.5)

Think in the business and not in the technology

Re: Major functionality addition to ASP.NET 1.1 application

You can use the same DB code, but its better to replace datagrid with Listview or gridview. The only disadvantage of migrating can be the time taken in migration and bug fixing due to migration. There are no other issues and migrating to the newer version will help in the long run. Vivek

Re: Should we migrate from ASP.NET 1.1 to ASP.NET 3.5

Addition of new functionality to existing ASP.NET 1.1 application will invlove creating new WebForms to store data.

As application already has custom User Management and user interface is implemented with WebUserControls, moving them to Master pages, User Profile etc will cause extra effort. Data access layer uses ADO.NET, rewriting it to LINQ to SQL/Entity Framework will take a long time. so even if we move to ASP.NET 3.5, application architecture/design and most of code will remain the same. Of course, we could use features like ASP.NET Ajax without major change.

The multi-targeting feature of Visual Studio 2008 lets you specify the .NET Framework version 2.0, 3.0, or 3.5, but not 1.1. ( http://msdn.microsoft.com/en-us/library/bb398197.aspx)

Re: Major functionality addition to ASP.NET 1.1 application

Thanks.

Addition of new functionality to existing ASP.NET 1.1 application will invlove creating new WebForms to store data.

Re: Should we migrate from ASP.NET 1.1 to ASP.NET 3.5

It's hard to advise on this but I would go to 3.5 - Chris Pells has done a neat video on the Listview control - which is good for CRUD type work. Unlike the Gridview the ListView is easy to customise -

Good luck let us know how it turns out.

Re: Should we migrate from ASP.NET 1.1 to ASP.NET 3.5

Thanks.

Is DataGrid deprecated in ASP.NET 3.5 ?

If so, why is it not mentioned in MSDN documentation here http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.datagrid.aspx ?

Re: Should we migrate from ASP.NET 1.1 to ASP.NET 3.5

DatagGrid is still included as a WebControl to support backwards compatibility. Else old applications might just break in newwer version and would force users to change controls even when the datagrid is working fine for their needs. So to support backwards compatibility such controls are included.

Vivek