All geek questions in one place

MVC in C # coexists with Webforms in VB. Could this happen?

I have inherited a really terrible web form application that is all kinds of bad - the elusive hairy mess of Page_Load datasets and events. Object Oriented? N-level? Unit tests? source control? All the academic subtleties for the team that built this mess.

This is the beginning of life as a classic asp application that has mostly ported to VB.NET. The management rejected my request to "destroy the entire site from orbit" and start all over again.

[Paste the discourse on how ASP.NET MVC is absolutely, positively the only normal way for .net sites anymore]

I know that we could interact between legacy web forms and mvc. The question is, can we leave the legacy code in VB and build new material in C #? I want to force the conversion to C # so that the team does not return to bad habits.

Is there an Arec MVC 2 strategy we could use here?

+3
source share
3 answers

I am not surprised that the idea of ​​a complete rewrite was brought down. In general, this is a recipe for delay and more errors, regardless of how buggy is in the current project.

, . -, , . , # - CLR, # . .

- -, "". , . , , web.config. .

: http://timheuer.com/blog/archive/2007/02/28/14002.aspx

, Google, . , .

, , - MVC . , . , , , .

+3

, VB. : , , , .

- , , VB, , . , , VB, , #. , , -, .

( VB, # #, , , , #.)

0

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

More articles:


All Articles