Can I use Response.WriteFile with a physical path across web servers? (ASP.NET)
We currently have two IIS webservers -- web and webapp. All of our static HTML files live on web and all of our old ASPs and newer ASPX files live on webapp.
An outside consultant is redesigning our website look and feel and has given us all new HTML pages, CSS files, etc. which are all going to live on web. We're in charge of modifying all the ASPs and ASPX files in house to get them to match the new look and feel.
For testing, we had just copied the template files over onto webapp and were using Response.WriteFile("/ssi/h
However, we really don't want to have duplicate ssi folders on both web and webapp to maintain-- we'd like to keep all the header/footer files on just web -- problem being, if we do something like this: Response.WriteFile("http://web/ssi/header.shtml"), we get the error: 'http://web/ssi/header.shtml' is not a valid virtual path.
Is there a cleaner way to include our header and footer files across web servers?
An outside consultant is redesigning our website look and feel and has given us all new HTML pages, CSS files, etc. which are all going to live on web. We're in charge of modifying all the ASPs and ASPX files in house to get them to match the new look and feel.
For testing, we had just copied the template files over onto webapp and were using Response.WriteFile("/ssi/h
However, we really don't want to have duplicate ssi folders on both web and webapp to maintain-- we'd like to keep all the header/footer files on just web -- problem being, if we do something like this: Response.WriteFile("http://web/ssi/header.shtml"), we get the error: 'http://web/ssi/header.shtml' is not a valid virtual path.
Is there a cleaner way to include our header and footer files across web servers?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.