Hi Morgan,
As for the problem that some times the .NET will looks for these files in
system32 folder, this is because when you using some dotnet apis they will
call some system api internally which will mapping the current path(haven't
specified path) to the system32(their dll's path). In web application, we
can use the Server.MapPath or
Response.MapPath to mapping the current web context's virutal path to
physical path on the server's disk, for example:
Response.Write("<br>Current path: " + Request.MapPath("./"));
Response.Write("<br>Site Root path: " + Request.MapPath("/"));
Response.Write("<br>Application Root path: " + Request.MapPath("~/"));
Response.Write("<br>Current's Parent path: " + Request.MapPath("../"));
For more detailed information on the "MapPath" method, please refer to the
following link in MSDN:
#HttpServerUtility.MapPath Method
http://msdn.microsoft.com/library/en...webhttpserveru
tilityclassmappathtopic.asp?frame=true
#Server.MapPath
http://msdn.microsoft.com/library/en...rommp.asp?fram
e=true
Hope helps. Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx