Jeff Cochran wrote:
First, Windows determines a file handler by the file extension. It's always worked this way. Unix has never used extensions and instead the file type is contained in the file. So any attempt to remove extensions in any Windows-based system is frustrating at best and futile at worst.
Second, you have no reason to hand out URLs with a file name. You can use a redirect, either in DNN or in IIS, to direct a URL to a specific URL with file name. You can also use the IIS default document to determine what file is served when a request for the site/folder is made. Your business card doesn't need to show http://www.sample.com/default.aspx when the URL sample.com responds with the same page.
If you really have to have extensionless file names, the proper way to do it is by not using a Windows-based product.
Jeff
I think you're missing the OP's point here.. DNN doesn't actually create a physical .aspx-file for every page you create.. Instead, you must pass the pages' TabID in the URL, to go directly to that page.
If for example, the OP has a specific page with a sample title 'Seminar 2011' with ID '40', the direct URL would become something like
http://www.theopsdotnetnukesite.com/S.... It would however be nice if there was an easy default way in DNN to define a custom URL-alias (for example:
www.theopsdotnetnukesite.com/seminar2011) that redirects/forwards to the former.
Now you tell me; which of both would
you choose for putting on your businesscard?
