Click here to Skip to main content
12,511,648 members (45,675 online)
Rate this:
 
Please Sign up or sign in to vote.
See more: ASP.NET MVC
lot of companies are considering converting their existing applications made in Asp.net to asp.net MVC and also considering the performance issue with asp.net w.r.t asp.net mvc do u think an web application made in asp.net also can standard in market 1-2 years from now???
Posted 26-Aug-12 19:56pm
sp1786668
Comments
ryanb31 27-Aug-12 11:22am
   
Yes.
deepakaitr12345 4-Sep-12 7:52am
   
Yes there are few constraints that are really good for the MVC development.
but the normal asp.net application will stand from 1-2 year from now that must be develped as per the page life cycle provided by microsoft.

Thnaks
Rate this: bad
 
good
Please Sign up or sign in to vote.

Solution 1

Seeing the current scenario it seems that almost all .net projects are moving towards MVC. It would not wonder if there are all new projects being made in MVC.
  Permalink  
Rate this: bad
 
good
Please Sign up or sign in to vote.

Solution 2

asp.net will never die.. asp.net has the rich set of controls which do not fit into asp.net MVC framework.. No matter how much asp.net mvc is preferred, asp.net webforms will always be there
  Permalink  
Rate this: bad
 
good
Please Sign up or sign in to vote.

Solution 3

Personally, I much prefer working with the MVC framework. Considering the way the web is moving, with more and more sites being accessed by mobile \ smartphones, UIs are becoming more lightweight HTML with javascript components for client side interactivity.

The MVC pattern fits more naturally into the stateless nature of the web, and the overall feel of the framework is geared towards this. I always felt that webforms tried to bridge the gap between 'traditional' VB6 forms design and the web, which while was helpful in taking the learning curve out of people moving into the .Net framework (many years ago!) didn't truly represent the web.

At the company I work for, we still have many Webforms 'administration' applications that have been around for years. They still work, they do their job, they are internally used so we don't have to consider mobile or cross browser considerations - in my opinion it's not worth the man hours to redeisgn them in MVC just because we can.

However, for all new developments, we're definitely using MVC. Anything customer facing is strictly using MVC, with backbone or knockout based UI designs. With MVC we get a brilliant continuous intergration environment with Team City, with unit tests and UI tests run as part of every check in. It's simple and it works.
  Permalink  
Rate this: bad
 
good
Please Sign up or sign in to vote.

Solution 4

ASP.Net will long last. Do not worry.
  Permalink  

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month


Advertise | Privacy | Mobile
Web02 | 2.8.160929.1 | Last Updated 5 Sep 2012
Copyright © CodeProject, 1999-2016
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100