Top ten considerations while migrating from .Net 1.1 to .Net 2.0 Web Applications
- Use the Web Project Conversion Wizard
- To ensure browser compatibility XHTML compliance has been enforced in .Net 2.0, one good idea would be to run your aspx pages through an XTHTML parser and fix any broken pages.
- If current .Net 1.x applications use AJAX framework, either convert them to ATLAS (preferred) or build applications with the corresponding AJAX 2.0 libraries.
- In usage of Object model calling a protected constructor directly is not allowed for security reasons, but calling through base constructor is permitted.
- You should consider Re-designing the entire layout to a Master page layout.
- Use more ATLAS components to reduce post back delays
- Re-visit pages that were cached to support Sql Notifications hence reducing rounds trips between database and application layers.
- Re-organize complex screens to use the new Wizard control.
- For more organized and easily maintainability of code convert the entire aspx codebase to partial classes.
- Use Site Navigation features of ASP.Net 2.0 to manage breadcrumbs with ease.
Reference Links:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/webprojectsvs05.asp