MD said:
Technically yes as it will be seen by the server as requiring ASP.net
support. However, unless it contains some ASP code you could not
consider it a .net page.
Not really. If you don't have the file extension mapped in IIS, IIS will
serve it simply as an HTML page and no code will run. Making it .aspx
doesn't cause the server to see it as requiring ASP.NET.
It also doesn't require any ASP.NET code to be considered an ASP.NET page
(although it's significantly less useful without code.) What makes it an
ASP.NET page is when the request for it is handled by the ASP.NET
architecture. If ASP.NET is registered with the server, the request for a
..aspx page will be handled by the PageHandlerFactory HttpHandler.
The .mspx file extension is a file extension that Microsoft uses on some of
their sites. They have written a custom HttpHandler for those pages (one
that controls the caching of the page among other things) and mapped the
..mspx file extension to that HttpHandler. You can create your own
HttpHandler (likely beyond the scope of what you're doing) and then create
your own file extension to map it to. That extension could be anything
(like .robin) and then requests for those pages would be handled by your
HttpHandler.
That answer is probably more than you asked for, but now you know.
--
Jim Cheshire
JIMCO
http://www.jimcoaddins.com
Free add-ins for FrontPage
Author of Special Edition
Using Microsoft Office FrontPage 2003