The client I am building this for has an issue with keeping the wc.dll on the root. He really insists on putting it in a cgi sub-directory because he insists that the directory where the dll lives needs to have sripts and executible rights in order to work. If that's true, why is the dll installed by the framework on the root? Is there a way around that?

>>Rick,
>>
>>We are not using a virtual directory in this case. The reverse path works for showing the graphics, but the FrontPage extensions are not working correctly, and I am not sure how to fix that. I am using expandtemplate to display the page. The page itself is very simple. If I move the dll back to the root everything works fine. I can't seem to make it work using a scriptmap. Any suggestions?
>
>Frontpage extensions only work on files with extensions that FrontPage understands. This means HTM, HTML, ASP etc. To make this work you can name your templates with these names... I think you can also use some no longer needed extensions such as IDC and HTX (both from the Internet Data Connector).
>
>In general I would stay away from FrontPage extensions in your script pages as there may be issues in how those get accessed. In addition there's some overhead for those extensiosn and they've been known to crash Web Servers consistently without any indication of where the problem came from.
>
>+++ Rick ---
>
>
>
>>
>>>James,
>>>
>>>Whenever you reference a URL in a specific directory it becmes the active directory. So if you ref:
>>>
>>>/cgi-bin/wc.dll?somequerystrign
>>>
>>>/cgi-bin becomes your current directory. If you now reference an image with:
>>>
>>>images/someimage.gif you're actually saying look in:
>>>
>>>/cgi-bin/images/
>>>
>>>for the image. Of course there's no image there.
>>>
>>>As Michel suggest you either have to use a more absolute URL off the root (/somvirtual/) or you have to use reverse pathing. For example if your structure is:
>>>
>>>/yourapp/
>>>/yourapp/images/
>>>yourapp/cgi-bin/
>>>
>>>You can use:
>>>
>>>../images/someimage.gif
>>>
>>>to get to the image too.
>>>
>>>If possible always use relative pathing like the latter as it makes the app more portable.
>>>
>>>Another alternative that bypasses this whole mess with cgi-bin is to use scriptmaps. Using scriptmaps it doesn't matter where the actual DLL sits and you can 'naturally' reference any links via the scriptmap in any location.
>>>
>>>
>>>+++ Rick ---
>>>
>>>>I created a West Wind app and am now getting ready to roll it out. I want to put my exe and wc.dll in a cgi_bin subdirectory underneath my webserserver main directory.
>>>>
>>>>c:\inetpub\wwwroot\myproject\cgi_bin
>>>>
>>>>Everthing works except it can't find the graphics. It keeps looking for the graphics directory under: c:\inetpub\wwwroot\myproject\cgi_bin\graphics. The graphics directory is c:\inetpub\wwwroot\myproject\graphics.
>>>>
>>>>Does anyone know how to resolve this issue?