T
Tim_Mac
hi,
i am trying to find the best way of making a single .aspx page
available to any web site on an IIS 6 server. without having multiple
copies floating everywhere.
previously i have used a hardlink for the file and junction point for
the Bin directory, which works well. but not everyone is comfortable
doing this, and it doesn't scale well for many sites if using a GUI
tool such as NtfsLink.
i looked at using a HttpHandler for MyPage.aspx in the global
web.config for the server, but to my knowledge that only means i can
run server side code when a user requests MyPage.aspx. i want to
display the .aspx page and execute its code behind. i'm not sure how
to wire the two together with the global HttpHandler.
any ideas?
many thanks
tim
i am trying to find the best way of making a single .aspx page
available to any web site on an IIS 6 server. without having multiple
copies floating everywhere.
previously i have used a hardlink for the file and junction point for
the Bin directory, which works well. but not everyone is comfortable
doing this, and it doesn't scale well for many sites if using a GUI
tool such as NtfsLink.
i looked at using a HttpHandler for MyPage.aspx in the global
web.config for the server, but to my knowledge that only means i can
run server side code when a user requests MyPage.aspx. i want to
display the .aspx page and execute its code behind. i'm not sure how
to wire the two together with the global HttpHandler.
any ideas?
many thanks
tim