I need to change a asp.net project to HTML 5 supporting responsive design but not using MVC

Question

0.00/5 (No votes)

See more:

Hi,

I have a requirement. We already have a web application developed in asp.net using 3 tier architecture. Now we need to change the application and use HTML5 for desiging new layouts. This application should support Responsive design. But this application as of now need not be using MVC as this would need a change in the architecture level. I need guidance and suggestion from you experienced guys on how to proceed.

Thanks in Advance

Posted 8-Apr-14 4:21am

Dinesh.V.Kumar

Updated 8-Apr-14 4:42am

Richard C Bishop

v2

Add a Solution

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)

Raul Iloc · Accepted Answer · 2014-04-08T06:01:00

1.The ASP.NET web forms use basically server side controls that generates the javascript code needed to postback the data to the server, mantain the state of the controls between postbacks, and so on. So these those ASP.NET controls generate too much code and a excessive number of roundtrips to the server, so it is not very recommended to use webforms.

2.HTML5 is mainly client side, so it has very little to do with the webforms server controls. It's a different approach than the old ASP.NET webforms. Because of this, ASP.NET is including on its newer versions the MVC framework, the razor engine, JQuery and another javascriprt libraries. MVC includes some helper classes and templates that helps you generating the client code, and many other features to support HTML5 enabled webs.

3.Because now your code behind for managing user actions from the web pages are very linked to ASP.NET events model and with ASP.NET controls, the best solution that I recommend is to use ASP.NET MVC, and the changes will be mainly at the UI level, and the new controller classes will implement the user actions that in your case should be reimplemented even if you don’t use MVC.

4.So I don’t see any major architectural change in using ASP.NET MVC! You have just to replace the old "ASP.NET Web Forms" project with a new ASP.NET MVC project, then in your controller to use your existing Business Logic Layer.