views:

482

answers:

5
+2  Q: 

What is .MSPX?

I've noticed a lot of microsoft sites have the *.MSPX extension. While I'm very familiar with ASP.NET, I've not seen this extension before.

Does anyone know what this identifies?

+1  A: 

I think it's an XML based template system that outputs HTML. I think it's internal to MS only.

Booji Boy
A: 

Well, a little googling found this:

The presentation framework includes a custom Web handler built in ASP.NET. Pages that use the presentation framework have the .mspx filename extension, which is registered in Microsoft Internet Information Services (IIS) on the Web servers. When one of the Microsoft.com Web servers receives a request for an .mspx page, this custom Web handler intercepts that call and passes it to the framework for processing."

I'd like to find out more info though.

FlySwat
+1  A: 

An article on it is still available, courtesy of the Internet archives: http://web.archive.org/web/20040508051618/http://www.microsoft.com/backstage/bkst_column_46.mspx

Mark Cidade
+4  A: 

A few internet searches led me to http://www.microsoft.com/backstage/bkst_column_46.mspx, but it was a dead link. Fortunately, it was archived on the Wayback Machine and you can read it here:

http://web.archive.org/web/20040803120105/http://www.microsoft.com/backstage/bkst_column_46.mspx

The .MSPX extension is part of the "Microsoft Network Project," which according to the article above, is designed to give Microsoft's sites a consistent look-and-feel worldwide, as well as keep the design of the site seperate from the content. Here's the gist of the article:

"The presentation framework includes a custom Web handler built in ASP.NET. Pages that use the presentation framework have the .mspx filename extension, which is registered in Microsoft Internet Information Services (IIS) on the Web servers. When one of the Microsoft.com Web servers receives a request for an .mspx page, this custom Web handler intercepts that call and passes it to the framework for processing.

The framework first checks to see whether the result is cached. If it is, the page is rendered immediately. If the page is not cached, the handler looks up the URL for that page in the table of contents provided by the site owner (see below) to determine where the XML content for the page is stored. The framework then checks to see if the XML is cached, and either returns the cached content or retrieves the XML from the data store identified in the table of contents file.

Within the file that holds the content for the page, XML tags identify the content template to be used. The framework retrieves the appropriate template and uses a series of XSLTs to assemble the page, including the masthead, the footer, and the primary navigational column, finally rendering the content within the content pane."

A: 

I love you guys, i was asking myself also many times, why MS uses .mspx and what it is at all?! :)

That time i couldn´t find any informations quickly and assumed it would just be something on top of asp.net or maybe not even that, because you should be able to assign the same asp.net cgi dll to .mspx also easy too ;)

But, surely, it can be anything.. also an "special" CGI itself (completely beside ASP.NET), which processes that request with much better / much more cache-use, easier editing and so on..

The end of the story was, that i came accross the view, that maybe it´s not important to know, what .mspx exactly is :)