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.
user_one
Member
15 Points
45 Posts
Re: Should we migrate from ASP.NET 1.1 to ASP.NET 3.5
Jul 27, 2008 08:37 PM|LINK
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)