ASP. NET MVC also uses ASP. NET pipelines - so most of HttpModule base stuff works with ASP.NET MVC However, actual handler works quite differently - ASP.
NET Webforms uses Page and Control trees while ASP. NET MVC uses completely different approach - controller handling request and view used for html generation. There is certainly a learning curve involved for migrating to ASP.
NET Webforms to ASP. NET MVC You should be asking yourself what exactly would you gain by migrating to ASP.NET MVC - for example, do you get a lot of enhancements and viable life span is more than 2-3 years. These might be the few reasons for considering migration.
ASP. NET MVC also uses ASP. NET pipelines - so most of HttpModule base stuff works with ASP.NET MVC.
However, actual handler works quite differently - ASP. NET Webforms uses Page and Control trees while ASP.NET MVC uses completely different approach - controller handling request and view used for html generation. There is certainly a learning curve involved for migrating to ASP.
NET Webforms to ASP.NET MVC. You should be asking yourself what exactly would you gain by migrating to ASP. NET MVC - for example, do you get a lot of enhancements and viable life span is more than 2-3 years.
These might be the few reasons for considering migration.
Let me pull out my crystal ball. Since you really don't give much information, I'll have to read your mind... Hmmmm.... all signs point to no. Yes, membership works fine in MVC, but porting an app from webforms could mean a lot of issues, particularly if you rely on third party controls.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.