Using my own file extensions...

[Mhtml]

Ok, now Whammy told me before I can include a file with any extension I like. I can even load that file in my browser and if it's asp the scripts still get executed with no problems.

What problems may I face by using my own file extensions? Reason for asking is I wish to make a series of asp scripts SERIES X and I want to use .x as the extension which works but there may be a downfall I am missing.

[scroots]

i don`t think there is a downfall as long as your server is configure to execute .x like .asp


scroots

[Mhtml]

Buts that the thing, I haven't configured my server to do it yet it does. Bonus?

The problem with having to configure the server would mean I couldn't really distribute the applications.

I'm still devided over this, because it may only be my server (pws4.0) which executes it like that. I will have to test it I guess.

Well, you peeps can help me. If you have a site on an ASP capable server then try naming something .x and see if it get executed.

[brothercake]

You would have to make the assocation - I'm not familiar with ASP specifically, but there will be a config file of some sort in PWS which you use to make that symoblic link.

If I were doing this with Apache/PHP it would be

AddHandler application/x-httpd-php .x



For a distributed application I would have thought (but can't say for sure) that all you have to do is make that association in windows as part of the install program; maybe things like InstallShield can make that easier.

[oracleguy]

I know you can make a program that will add an association to IIS, i mean the PHP install does it when you install it on IIS.

[glenngv]

In the IIS console, you can map a file extension to execute it as an asp file.
Default Web Site->Properties->Home Directory tab->Configuration button->App Mappings tab