Not understanding IIS Classic and Integrated Mode?

There is a good explanation here pointing out the difference between Classic x Integrated mode in IIS:

https://help.maximumasp.com/KB/a657/explanation-of-classic-vs-integrated-mode-in-iis-7x.aspx

Also here's an explanation of the ISAPI extension:

http://msdn.microsoft.com/en-us/library/ms525172(v=vs.90).aspx

My question is: Is the application I am developing (ASP.NET MVC Application) an ISAPI extension? I am asking about this because it is not very clear to me.

Also, from the first link:

In classic mode, the server uses two lines to process requests, one for native code and one for managed code. In this mode, the application does not take full advantage of everything IIS 7.X has to offer.

Integrated mode handles all requests through a single pipeline for IIS, and is tightly integrated with ASP.NET through the same pipeline. ASP.NET sees every matching request and manipulates things rather than acting like an external plugin.

• What is the king of benefits integrated mode offers?

From the second link:

IIS uses the virtual location of the DLL file in the file system to map the ISAPI extension to the URL namespace that is served by IIS

Suppose the request is being made to IIS: "http: // localhost".

• What will be the URL namespace that IIS serves? Where is the virtual DLL location?

Sorry for those new questions. I am new to Windows development, so it is difficult for me to understand these functions.