Is there any article that introduces the complete flow of round-trip requests to MVC-based web sites. For example, when OnActionExecuting (under Controller) will be executed during the request life cycle.
Thanks.
This should help:
http://blog.stevensanderson.com/2007/11/20/aspnet-mvc-pipeline-lifecycle/
there are a few useful ones here too on MVC: http://devcheatsheet.com/tag/aspnet-mvc/
Scott Hanselman explains a littlebit in his ASP.NET MVC2 demo.
Related
I am new to ASP.NET MVC and have worked in ASP.NET before. I am starting a new project in ASP.NET MVC 2 and wanted to find out what all state management techniques are available in ASP.NET MVC 2.
Can anyone please suggest some good resource.
Thanks.
You can use Session just as in ASP.NET WebForms. Was there anything else you wondered? You don't have ViewState as in WebForms, but you can use ViewDatato pass data between controllers and views (see e.g. http://msdn.microsoft.com/en-us/library/dd394711.aspx). What kind of state are you planning to manage?
For state management you can use Session, but to do it the MVC way, you should combine it with action filters.
Here are some links that can help you:
ASP.NET MVC Filters and Statefulness
mvcConf 2 - Brad Wilson: Advanced MVC 3
I just learned about the existence of the PRG pattern, and I'm wondering if ASP.NET MVC 2 or above implements it out of the box. If not, are there any relevant examples or tutorials? I've seen some for MVC 1, but I'm not sure if they're still relevant.
Yes, it has support for it. But classic asp.net does have the support too. It's just about redirecting the page after post. In MVC, in your Create/Update/Delete action you implement the PRG by returning RedirectToAction instead of View.
See, for example, https://blog.iannelson.uk/an-mvc-gotcha-and-the-prg-pattern/ for detailed explanation.
This might be the most trivial question asked, but I raise it again. Am planning to get started with asp.net MVC on a personal project and here am struck if it supports webparts or any other alternative to it is present. I intend to have a start page similar to igoogle or pageflakes, but my initial research pointed out that as there's no ViewState nor Postback concepts in ASP.NET MVC implementing web parts is not possible.
If that is the case, are there any resources which helps in building a start page as the one i wish to using MVC.
PS: Links I found in the initial research
Quick tips on asp.net MVC -
webparts framework
Building widgets using jquery in
asp.net MVC
You should use AJAX to create widgets that can interact with the server without reloading the page.
This way, the widgets will not affect each-other.
jQuery will be useful here.
Alternatively, you could put each widget in its own <iframe>.
I'm looking for some free ASP.NET MVC design templates for an internally facing web app. We don't have a graphic designer and I'm not good at that side of things.
Can anybody suggest some good links? All I've found so far is http://mvccontribgallery.codeplex.com/, but there's nothing there that suits.
Thanks!
You can make any html template compatible with ASP.NET MVC. Don't limit yourself.
Good Afternoon,
I'm rebuilding an event ticketing site originally developed using ASP.NET 3.5 WebForms and am considering using ASP.NET MVC2 for the rebuilt solution. I like the idea of friendly URLs as the current site has very long query string URLs for each specified event. MVC2 also appeals from a separation of concerns point of view as well. The biggest unknown for me is will MVC2 handle calls to 3 separate web services (SOAP and REST) to get ticket availability? That is, does the controller functionality permit use of such web services? Finally, MVC3 is due to RTM in January. Am I better off waiting for MVC3, or can I start the project in MVC2 and port it later?
Thanks for all your advice and insight.
MVC can handle any HTTP request as ASP.NET forms does. Indeed you should consider to use WCF for handling SOAP queries. And yes, sure you can easely create REST API with MVC.
It is better to start now, with ASP.NET MVC 3 RC2. It is very stable and nice. This will minimize migration work. Welcome to MVC happy world!
The controller will let you run pretty much any code you want.
I just started using MVC in a big project and it's turning out well. We went with MVC 3 and it's been a little tricky living on the edge, but it seems to have a lot of nice improvements. I'm extremely happy to be using MVC instead of Web Forms. To me, it seems to flow smoothly instead of fighting with the way the web works.