Hi Bob,
I suppose you also want to know how to use a hammer to screw in a screw?
ISAPI mappings are done through IIS. That is the tool to use for mapping
ISAPIs. VS.Net is the tool to use for developing software. You could,
ostensibly, write an extension for the IDE that enables you to set
configuration settings in IIS, but it sure would be a lot of trouble,
compared to opening the IIS Admin snap-in and doing it that way.
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
" Bob" <bo*******@yahoo.com> wrote in message
news:e4**************@TK2MSFTNGP10.phx.gbl...
I know how to set it up in IIS so IIS knows how to treat a particular
extension. My question was how to do it in VS.NET, the IDE. For example,
VS.NET displays .aspx different from .xml, how does it determine and more
importantly how do I customize?
"michael" <mp********@sbcglobal.net> wrote in message
news:em****************@TK2MSFTNGP11.phx.gbl... Go into IIS | Home Directory | Config and from there set the extension that you would like.
" Bob" <bo*******@yahoo.com> wrote in message
news:O$***************@TK2MSFTNGP10.phx.gbl... I noticed that some of the Microsoft site pages have the extension
name of mspx. It's easy to config IIS to map a particular extension name to
the ASP.NET dll for production purpose. However I can't figure out how to
config VS.NET to recognize my own file extension name e.g. *.bob, as ASPX
pages. Is it matter of creating a set of template? If so, would it compile
correctly? My goal is for VS.NET to treat a different extension name the same as aspx, so I can develop web pages with that extension name the same way I do aspx.
Thanks
Bob