8 Great Websites to Learn Step-by-Step jQuery

http://webdesigneraid.com/8-great-websites-to-learn-step-by-step-jquery/

Sequence diagram for ASP.NET application events in Global.asax

There are two types of events in global.asax file in your application domain:

1. Events which get called for every request.
2. Events only get invoked under certain conditions.

For the first type of events which occur for every request, they get executed in the following order:

1. Application_BeginRequest(): This is called at the start of every request.
2. Application_AuthenticateRequest(): This is called just before authentication is performed. You could add your own authentication logic in this method to provide custom authentication.
3. Application_AuthorizeRequest(): This is called when the authentication stage is completed. It's executed at the stage to determine user privileges and permissions. You could add custom code to assign user special privileges.
4. Application_ResolveRequestCache(): This is often used in conjunction with output caching. With output caching, the rendered HTML of a page is reused without executing its code. However, this event handler still runs.
5. ----------Then the request is sent to its assigned handler. For example, an ASP.NET web form page is sent to compilation (if it is due) and instantiation.----------
6. Application_AcquireRequestState(): This is called just before session-specific data is retrieved for the client and is used to populate Session Collection.
7. Application_PreRequestHandlerExecute(): This is called before the appropriate HTTP handler executes the request.
8. ----------The handler now executes the request. The code of your ASP.NET web form page is now executed and the HTML is now rendered.----------
9. Application_PostRequestHandlerExecute(): This is called just after the request is handled by its appropriate HTTP handler.
10. Application_ReleaseRequestState(): This method is called when the session-specific information is about to be serialized from the Session Collection so that it's available for the next request.
11. Application_UpdateRequestCache(): This is called just before information is added to the output cache. If you have enabled output caching for your web page, it's now the time ASP.NET insert the rendered HTML into the cache.
12. Application_EndRequest(): This is called at the end of the request, right before the objects are released and reclaimed. It's the place to add your cleanup code.

This diagram below can help you grab a better insight of this cycle:


In general, developers are more likely to provide handling code for Application_BeginRequest(log information for analysis, routing, etc.), Application_AuthorizeRequest(custom authorization and privilege etc.) and Application_EndRequest(log information for analysis, cleanup, etc.).
For the second type of application events which do not fire upon every request, there are six of them:

1. Application_Start(): This is called when the application first starts up and the application domain is created. This is the place for you to insert application-wide initialization code. For example, you may want to add code here which load and cache data, load some application-wide configuration setting, navigation trees and other static data and information which will stay persistent throughout the lifetime of your application.
2. Session_Start(): This method is invoked each time a new session begins, This is often used to initialize user-specific information. Some developers also use this to count the number of current active user session in the application.
3. Application_Error(): This is invoked whenever an unhandled exception occurs in the application. You may want to use this to perform some custom error handling logic application-wide.
4. Session_End(): This is called when a user session ends. A session ends when your code releases it explicitly or its idle time exceeds the set expiry timeout (by default 20 minutes, you may change it in your web.config). Developers typically add code here to clean up any related data. Note that this method is only called if you are using in-process session state storage (InProc mode, not StateServer of SQLServer modes).
5. Application_End(): This method is invoked just before an application ends. The end of an application can occur because IIS is shut down or the application is transitioning to a new domain in response to file updates or process recycling.
6. Application_Disposed(): This method is called some time after the application is shut down and the garbage collector is about to reclaim the memory it occupies (just like other objects' disposal in .NET). Note that it is already too late to perform critical cleanup at this point of time. But you may want to add code here to verify that resources have been released as a last-ditch safe-proof.

http://www.freewebdevelopersite.com/2011/03/21/application-events-in-global-asax/

What is relationship between WebMatrix, Razor, ASP.NET Web Pages and MVC?

WebMatrix: a stack and a tool

Let’s start with WebMatrix.  The term is actually used is two ways:

1. The WebMatrix stack contains a number of things that you get when you install it via WebPI:
   • The new ASP.NET Web Pages framework
   • The Razor templating engine
   • The WebMatrix tool (see #2)
   • IIS Express
   • SQL CE 4
2. The WebMatrix tool, which lets you perform various tasks:
   • Create web apps that use the Web Pages framework and the Razor templating engine
   • Install existing sites from the Web Gallery.  Note that those sites don’t have to use the Web Pages framework, and in fact most don’t (e.g. ScrewTurn wiki, Subtext)
   • Manage IIS express
   • Manage SQL CE 4 databases

Key point: the WebMatrix tool is not by any mean the only way to create Web Pages apps.  In fact, the Web Pages framework was designed to be very notepad friendly.  On the other end of the tooling spectrum, it will later be fully supported by Visual Studio.

Razor: a templating engine

At its root, Razor is just a templating engine, which is best compared to something like T4.  It is also comparable to the aspx and Spark engines.  The best way to describe it in its most general sense is:

• It takes as input:
  • a template file (with a .cshtml or .vbhtml extension)
  • some input data: in web scenario, this includes things like an HTTP request, but this is not a requirement
• It produces some output string: in web scenario, this is typically a piece of HTML that then gets sent as an HTTP response, but it could be anything.

So as an example, you could envision a very simple command line tool that would read an input file and some parameters, and write out the result of running the template on that input.  Note that everything I wrote here applies both to Razor and to something like T4.

Key point: Razor in itself is not tied to MVC nor to the Web Pages framework, and is not even really tied to web applications.

Note: check out Andrew Nurse’s blog for lots of technical details about Razor.

ASP.NET Web Pages: a simple framework to write ASP.NET web apps

WebMatrix introduces ASP.NET Web Pages, which gives users a simple and powerful new way of writing ASP.NET apps.  It is different from WebForms as it doesn’t use server controls.  It is also different from MVC as it doesn’t follow the MVC pattern.  Instead, it follows a much simpler ‘inline page’ model, where a page is basically an HTML page with some code added where needed.  In that sense, it is reminiscent of Classic ASP, but it is also very different in the sense that it has the full power of the .NET framework available behind it.  It also supports concepts like layout pages which make it much more flexible than the Classic ASP.

Where the discussion gets interesting is that the Web Pages framework uses Razor as its default templating engine.  However, it is not tied to Razor.  Potentially, you could use the aspx or Spark templating engines with the Web Pages framework.  At this point, we have mostly focused on using Razor with it, but it’s entirely conceivable that other templating engines would be supported later.

Key point: ASP.NET Web Pages uses Razor by default, but is not technically tied to it.

ASP.NET MVC

ASP.NET MVC is not part of the WebMatrix release, as it is a completely different framework with different goals (and this post is not about the pros and cons of the two, so I won’t go into that here!).  However, it ties into the story because the Razor templating engine will (soon) be made available as an MVC view engine.  As it should now be clear, this does not imply that you would be using ASP.NET Web Pages if you choose to use Razor as your MVC view engine.  All it means is that you’d be using the Razor syntax for your views instead of aspx (or Spark, …).  This has no bearing on how you write your controllers or other parts of your app.

Key point: Razor syntax will soon be available as an MVC view engine alternative

How WebMatrix, Razor, ASP.NET Web Pages and MVC fit together - Angle Bracket Percent - Site Home - MSDN Blogs

Generating RSS and ATOM Feeds In WebMatrix

Generating RSS and ATOM Feeds In WebMatrix

Asp.net MVC A-Z

Action:-Actions are like our general methods we are writing in C#,Controller can contain all actions which can send the response to the user or calling Views. Action(s) have return types ActionResult ii will return ViewResult for calling the View

Controller:-It is the Heart of Asp.net MVC, which take request for user and it will decide what view to render. It contain actions.
Model:-Model is like our normal .net component for write our business logic/validations etc.
View:-It is rednering User Interface, it contain 2 forms either .aspx(View) or .ascx(Partial View)
ViewEngineCollection:-It gives list of all register views

http://mvcframework.wordpress.com/2010/04/22/asp-net-mvc-a-z/