ATL Server include issue....
-
Hello, Here is the problem I have run into. I have an Atl Server Web App that is structured like the following: \bin (dll's) \include (common srf that get included) \secure (srf pages that need to be under SSL, also needs access to inlcudes) *.srf general srf pages that need access to the includes Here is the problem, when one of the general srf files uses an include the path for the include internal handler is \bin\something.dll. The path used for the include is relative to the file that included it, not the include itself. Now when one of the secure pages includes the same file the handler path to the dll is wrong, it tries to load the library from ...secure\bin\something.dll. This causes an issue, if the handler paths were relative to the actual file being rendered all would be well. Has anybody run accross this before and have any suggestions? Seems like the alternative is assign SSL access on a file by file basis? Other than this issue ATL server seems like a slick framework! Thanks for any suggestions!