asp.net webforms Vs MVC ?

Question

0.00/5 (No votes)

See more:

Hello,

I am working on one big project which is implemented in asp.net web-forms (VS-13). Now My Head told me shift on MVC because it gives a good performance. My asp.net web-forms project took 4 months to complete. Now please tell me Is really good to go for MVC for performance purpose? can I achieved same performance with web-forms? and how much time/months I required to implement same project in MVC as i am new one in MVC.

thank you.

Posted 6-Sep-15 18:19pm

Member 11922776

Add a Solution

Comments

aarif moh shaikh 7-Sep-15 1:04am

you should go with MVC.

Member 11922776 7-Sep-15 1:18am

how many months i required? as I am just start today with MVC.

Member 11922776 7-Sep-15 3:00am

aarif sir please reply. how many months i required? as I am just start today with MVC. it's urgent. I know its also depend on me. but i want suggestion from experience person.

F-ES Sitecore 7-Sep-15 4:36am

Whether your project will be any quicker using MVC depends on how you've developed it using webforms. MVC isn't inherently quicker itself, it's just a "different way" to write web apps. If you have any kind of benchmarking or profiling tools you can look at your existing project to see what the worst performing aspects of it are.

If it took you four months to do it in webforms then I'd imagine it may take the same again in mvc. Where you'll probably struggle the most is if you've used things like gridview controls, as there are no real MVC equivalents, and writing that stuff yourself tends to need a good grasp of html\http which webforms shields you from having to know.

To sum up: your head is listening to too much rubbish on the net about the benefits of MVC, it's possible to have your webforms site still perform as well as mvc however if you're lacking experience that might be a struggle.

Member 11922776 7-Sep-15 5:50am

Use of three tire architecture is same as MVC if we consider just coding part not front-end or is it affect a performance? Which tool should I used for checking performance of my project(web app)? Now the fact is this is my senior's project now handover to me, and he did a complete plain coding i.e. No use of moduler programming,he wrote a code like one aspx page and its .cs file contain 8000 of lines. same for all other pages.
thank you for u r time and reply.

F-ES Sitecore 7-Sep-15 6:03am

It's the classic argument...people write a bad webforms app and think that converting it to MVC will cure all their problems. If the existing webforms app is a mess then converting it to MVC will allow you to completely refactor how the app is written and make it more modular and easier to maintain.

Never really used profiling tools myself, but if you google "asp.net profiling tool" you'll probably get some examples. For basic timing etc using the network tab on your browser's dev tools will give you some basic metrics such as how long it took, the page size etc, and I know there are online tools that can analyse this stuff for you too.

Member 11922776 7-Sep-15 6:33am

so what would be u r suggestion sir, go for MVC or make existing one in three tire?

thank you once again.

F-ES Sitecore 7-Sep-15 6:36am

It's up to you really, it would be quicker to just sort out the existing webforms app to make it tiered. Once you've done that, if you do still want to move to mvc then the task will be easier as all the business code etc is abstracted away into its own layers and you can just move that code across to a new project, leaving only the presentation layer to rewrite. The biggest issue going from webforms to mvc is if you have a lot of code and logic in the aspx.cs pages.

Member 11922776 7-Sep-15 6:50am

yes sir that's what issue i am facing now.have a lot of code and logic in the aspx.cs pages. ok now i am making it modeler first. then go for MVC.

thanks to you and all for valuable suggestions.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ) · Answer 1 · 2015-09-06T18:43:00

Solution 1

I think all your questions will be answered here - WebForms vs. MVC[^].

Posted 6-Sep-15 18:43pm

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ)

Comments

Member 11922776 7-Sep-15 1:17am

Sir I go through most of links also WebForms vs. MVC[^]. but at final conclusion is both can't replace each others. and questions also provided that to choosed which one. but I am completely new in MVC. so which one is good? MVC as aarif said?

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ) 7-Sep-15 3:49am

If you are new, then it will definitely take some time to grasp the concepts first and try some demos. In web forms app, many things and controls are staright forward, but in MVC they are not. You have to get those skills, but it would not take much time though.

If you have some time, then go with MVC, because future is MVC.