My organization has many inherited ASP software that is on its hands.
Since our perception is that Microsoft is seeing a specific lack of support for its old products, we should know how to migrate to move to the next.
If we transfer ASP.NET from classic ASP, then it seems that 'full rewrite' 'migration' 'Since this is probably the case, we have a free (as beer and speech Are thinking about changing the platform). I especially feel that our investment (in programming effort, I mean) will better spend with a platform that will develop us, instead we are forced to dump the same line of code for every 4/5 year Done This is the main argument that we are experimenting to advocate to move towards 'free' platform.
We are currently thinking of using Java as a dynamic language such as the Jerubi or Groovy.
My questions are: What will be a good migration option? Are our fears unfounded? Would we want to re-write (concepts) a large part of the codebase after 4 or 5 years? Which logic do you have on the NAT or any free forum?
We have recently had enough ASP projects for ASP.NET and it is certainly possible that It is possible to do a migration, which does not preserve a strong proportion of the original code (though we are benefiting from some well-structured code with good separation between business logic and good
Seen two possible routes:
-
A 'reasonable' AS Replacing a ground-up in the form of P. In most NET applications, most of the built-in controls and all business and data access layers are changed into class etc. - that is, we approach a new ASP.net project.
< / Li> -
Other original syntax migration, taking ASP pages and changing them to ASP.NET without making too much front-facing changes in structure or logic. We can continue to develop the site through better use of ASP.NET controls and for new and improved functionality, through different sections etc.
We have another way , Which allowed us to switch later rather than later, and then take a longer view on more fundamental changes as part of future development.
On that basis, we were able to reuse most of the existing code for initial migration, although it is gradually being changed because we move forward. It is said, along with an 'average' page with 50-200 lines of HTML and 50-500 lines of VBSSPR code (in the form of different functions, which are not mixed in the HTML spaghetti-style), we found that They took about an hour per page to migrate, some simple pages, including access to all the new ADO.NET data access layer of ADO data took a few minutes - some of the complex pages took a whole day - but hundreds The pages consisted of an hour-to-one page, as well as the time to change the data access that represents an important part of the effort.
If we want to start the migration today, then we will use ASP.NET MVC instead of the web form because it was written to the original pages, as I wrote - although I do not comment Migration will take more or less time for MVC whether it can or does not.
It does not have any effect on whether you want to change the language by going to a free platform - you may have other reasons to do this (our customers were windows, so on ASP.NET There was no extra expense on the one hand moving the development time aside.) However, I can say that ASP.net is possible to migrate an important ASP site without a complete rewrite - and it is equally possible And is migrating from the previous versions of ASP.NET to more recent versions with minimal work. Obviously, the way on which we have chosen, some ASP can not be compatible with everyone, rather than choosing the code for complete redevelopment - but it gives you a low impact entry point in ASPNET, so that you can build it Is allowed. This base while availing the maximum benefit of your existing codebase and skills.
Comments
Post a Comment