I have a problem executing some ASP.Net pages in a certain setup...<BR><BR>I have a virtual directory setup on my local computer inside the wwwroot directory called EMSAssist. When I create a deployment project, the project gets placed on a test destination webserver called "www.nicemtech.com/emsassist". When I try to go back to the main menu from the following link (inside the website): "http://www.nicemtech.com/emsassist/Scheduling/Admin/MemberAdmin.aspx", it works fine without a problem...<BR><BR>A domain name has been registered (www.emsassist.com) where the website will now be deployed. When I try now to go back to the main menu from the website (from the following link: "http://www.emsassist.com/Scheduling/Admin/MemberAdmin.aspx", I get the following System.Web.Httpexception error: <BR>"Cannot use a leading .. to exit above the top directory".<BR><BR>I know this error has been caused by the following code in the aspx page that caused the error:<BR>&#060;code&#062;<BR>&#060;%@ Register TagPrefix="YTCIWebUserControls" TagName="SchedulingAdminLogout" Src="../../UserControls/NCVACEMT/SchedulingAdminLogout.ascx" %&#062;<BR>&#060;/code&#062;<BR><BR>It seems when executing from the test web server, it&#039;s fine (5 levels down from the root - http://www.nicemtech.com/emsassist/Scheduling/Admin/MemberAdmin.aspx). <BR><BR>However, when executing from the actual domain name, it crashes (4 levels down from the root - http://www.emsassist.com/Scheduling/Admin/MemberAdmin.aspx).<BR><BR>I&#039;m explicitly stating to grab my usercontrol from the following pathname (../../UserControls/NCVACEMT/SchedulingAdminLogout.ascx), which, doesn&#039;t exist in the domain name site because of the extra "../" in my path, but is fine with my testwebsite...<BR><BR>Is there any way for me to somehow seemlessly have the two different sites working without changing the pathname of the test site and production site to two different paths?