| [reply] |
While we are waiting for some details Anonymous Monk, let me fill you in on a little secret. I've told Y'all it before and I'll probably tell Y'all it again.... IIS likes full paths included with the filename. So it's not simply "testfile" it has to be "c:/this/is/the/complete path/to my stupid little/testfile"*, or whatever you happen to call your file. (What!??? I like silly names and paths for my files, don't you?) So if you want to require (do people still use that?) a file then you will need to require the full and complete filename with path.
* I have used slashes because it saves time and characters. Feel free to use double backslashes if you want too.
| [reply] |
The require statement will be interpreted the same whether PERL.EXE was invoked to run the script from IIS, Apache, a command line, etc. It'll always look for the file being required in the paths defined in the @INC array, and IIS can't do anything to change that. I use require and IIS all the time, and never include the path to the file being required. The web server is kind of "out of the loop" at that point. Unless by 'require' you don't mean PERL'S require statement, but something entirely different.
Do you maybe mean that its behavior is different when referencing files in VIRTUAL directories, somehow?
| [reply] |