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
Keep it Simple!!!
DRY
YAGNI
Last Responsible Moment
dacanetdev
Participant
1344 Points
218 Posts
Re: Should we migrate from ASP.NET 1.1 to ASP.NET 3.5
Jul 27, 2008 03:08 AM|LINK
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
DRY
YAGNI
Last Responsible Moment
If you like my answer don't forget to mark it.