Path Management on Local XP Development Machine?

[clintonG]

The hacks and work-arounds are cluttering up the elegant code I write ;-)

I locate projects at c:\Inetpub\wwwroot on my local development machine.
Learning and working on many projects requires using a subdirectory such as
c:\inetpub\wwwroot\projectname.

Okay, when running the applications for example this produces a path such
as:
http: //localhost/projectname/dir1/dir1.1/filename.aspx

Let's say I need to use the String.Split method to get some value out of
that URL which is very common. I have to write conditional logic to detect
the presence of the projectname directory and then write the code that is
actually needed.

This results in redundant code; some code for the projectname when building
on the local XP development machine and some for the Windows 2003 Server
where the code will be deployed in the root of the web where the projectname
subdirectory will not be required.

This has to be a problem for all of us developing on XP. I'm wondering what
tactics others have used. Keep writing redundant code or is there some other
strategy for development on an XP machine?
--
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/