Thank you very much.
I'm not hard coding anything from the root (nothing like
C:\SomeFolder\SomeOtherFolder\SomeFile.aspx). Rather I programmatically
determine the current application's root:
string m_appRootFolder =
System.Web.HttpContext.Current.Request.Application Path.ToString();
and then refer to folders under the root.
The problem I had was one of really understanding where my application root
was and the associated issues resulting from using the default XP/Pro
C:\inetpub\wwwroot\MyApp setup created by VS.NET. Everything's cool when the
app exists under the current Web site's root - but the production server
uses the root, itself. When I started this project I didn't think much about
it. Now I have to (simple, but important).
"WJ" <Jo*******@HotMail.Com> wrote in message
news:ey**************@TK2MSFTNGP10.phx.gbl...
"Jordan S" <A@B.COM> wrote in message
news:eT**************@TK2MSFTNGP12.phx.gbl... Thanks - so just to clarify, I think I'll be fine if I do the following:
1. Create any old folder I want (e.g., C:\MyWebApp)
2. In IIS, make it a Web application (with C:\MyWebApp as the root).
3. Move all of my application files and folders into it
On top of that, give appropriate access privilege to the web account that
runs the web site (not web server). Example: If you have a folder that
accepts user's uploaded files, then make sure to grant write access to the
appropriate account for that folder.
4. Fix all the path-specific logic throughout my app.
Sound like you are hard coding stuffs. If so, yes, clean them up, do not
hard code things such as "c:\sss\somthing.aspx". Example: If you want to
invoke Page2.aspx from a, say Default.aspx, then in Default.aspx, just
say: Response.Redirect("Page2.aspx");
Is this something you more experienced developers would do to fix my app?
Is there an easier/better way?
You may want to buy a good book about IIS, it is good to know inside out
although you need not to. This is the function of a web admin. not
developer.
John