ASP & # 8594; ASP.Net: Refactoring Steps

Question

I have an outdated ASP application that, at some point, needs to be ported to ASP.Net 2.0 (to be compatible with other applications that are also in version 2.0).

Are there any best practices for this kind of thing, i.e. is it possible / advisable as a first step to transfer the current inhuman mixture of html, vbscript and javascript en masse to aspx pages (without any code separation), and then iteratively replace vbscript with data sources and the like, or is it more of a problem than it value?

[The application is not so complicated (we say 10 or so .asp pages with the same number of .inc files), but the combination of html and scripts is not at all beautiful: a lot of if-else statements for creating SQL commands, etc.].

Answer 1

Vbscript may look like VB.NET, but there is a difference. In addition, calls to CreateObject should be replaced by calls to objects in the .NET environment.

I suggest you pull out the html parts and put them already on your pages, the same goes for javascript, images and css (basically they can be taken without much change (sometimes not at all) for your new application.

This article may also be of interest to you: Converting ASP to ASP.NET .