All geek questions in one place

What are some useful strategies for converting a classic ASP application to ASP.NET

We have a ten-year ASP application that we plan to upgrade. We want to use the new technologies offered by ASP.NET, as well as the ability to fix some problems with the existing infrastructure (the existing code base is highly fragmented, it is almost impossible to test, not to mention debugging, and the whole application was apparently built in accordance with " Agritourism. ")

To this end, it seems it's time to rebuild this application. But we are a small business, and we simply don’t have the resources to either hire a rebuild or devote our small development team exclusively to the recovery task (we have other tasks on our plate and cannot focus on this specific task for the time it takes to complete reconstruction of the application).

What are some useful strategies that we can use to help us transform this application without consuming all of our limited resources at the time of rewriting?

+3
source share
3 answers

, ; , (.. ), .

ASP classic ASP.NET , . ASP- ASP.NET, , - ASP.NET Web Forms ASP.NET MVC ( , ).

.NET- - COM-. 10- - ASP, .NET web services (.asmx), COM- .NET DLL . - .NET- ASP. .NET- - () ASP.

+1

. , - .

10- , , . , , , .

- ASP.NET MVC, ASP.NET WebForms - ? , . , - .NET ASP-, .NET.

+2

, , - . "", , , ASP.NET ASP, .

, ( " " ). , , , , . "" , , .

: " , ?" - , , . , , OLD , .

, ( - IIS), cookie/url session management, . , , - ( ) , Session.

If you do this at a time, make the pieces small enough and you have a good front design, this works well - at least in my experience, this is the way that works best. Please note that my experience may not be true.

0
source

Source: https://habr.com/ru/post/1763611/

More articles:


All Articles