Converting ASP 1.1 Website to ASP 2.0 Web Application

Yes, everyone is doing that one day or the other. It's my turn to convert a well-complex website to ASP.NET 2.0.

This website was using .NET remoting with SOA architecture, call to win32 apis, multiple libraries, url rewriting with custom .htm handlers etc. so it was a really complex website.

The steps to do that were really simple... Hoping so.

First I renamed the directory to a .old directory, so that, when converting the website to a ASP.NET 2.0 website, the wizard can create the 2.0 website in the original directory. Secondly I converted the website. But the problem is that I don't want a Asp.net 2.0 Website, but an asp.net 2.0 web application, the differences are explained here.

So, I just created a new ASP.NET web application, with the original path, and copied the whole site into it. If sourcesafe was enabled, It will prompt you do check out the old 1.1. project (!).

After that, I converted it to a web application, so that the .designer.cs are generated. After that, I compiled and found out some conversion issues, like some control, that were case insensitives in 1.1, when they was modified after being created in the code-behind file.

Everything was compiling... with 26 warnings, but compiling. (Almost deprecated code ClientScript, Configuration sections etc.)

ref:

How to: Convert a Visual Studio .NET Project to Visual Studio 2005 

Walkthrough: Converting a Web Site Project to a Web Application Project in Visual Studio 2005 

-f.