JQuery Mobile Directions ASP.NET or MVC

I am working on a large healthcare organization as a web developer, and recently I was tasked with developing a set of standards and possible reference applications for mobile development. Our current methodology relies heavily on asp.net 3.5 along with a large framework library that is common to all of our applications.

I was just starting to stumble with jQuery Mobile, and it seems that any solution or direction that we come up with will strongly depend on this structure.

Questions:

  • Is it wise or not to try jQuery Mobile's solution on top of asp.net web forms? I understand that jQuery Mobile does not use feedback in the traditional form of web forms, but can this be done? How much better will the MVC solution be? (I worked with both and don’t want to join the larger version of Web Forms vs MVC, but I wonder if it’s better to work with jQuery Mobile than the other.)

  • How is data stored in jQuery Mobile? I get the idea of ​​data-role = "page", but data is usually stored on the internal web server through ajax calls that do not rely on traditional client backlinks? If not, how? If he usually relies on ajax, then the idea of ​​using Web Forms is just plain stupid?

Thank,

+5
source share
1 answer

. - asp.net( ) - MVC 3 API.

jQuery Mobile, , . , , jqm Core Service.

. , , , , . , MVC 4 jQuery Mobile, .

  • , , - asp.net jQuery Mobile ( ViewState). , , , - asp.net MVC- - , , HTML, ASP ViewState.

  • jQuery Mobile. MVC , , ajax, . , / ajax- data-ajax="false" ajaxEnabled. , - Session . , , . , , ajax, MVC .

, , ( ) MVC ... , , , - asp.net jQuery , MVC.

, !

+1

All Articles