views:

101

answers:

2

I have several partitions on this laptop (XP, vista, 7rc1, and a clean partition for testing and installing foreign softwafe). I code on XP and windows 7. 4 partitions are already used so i have no spare partitions for my dev files.

What can i do to create a consistent dev path? I tried sharing my C drive and map T to /home/c however that caused a problem with my ASP.NET project. I get a error "Required permissions cannot be acquired.". When creating a new project i get an untrustworthy error. So what can i do to get Consistent dev path that will work with ASP.NET paths?

+1  A: 

If I understand what I think you're saying, you want your development files to be on their own drive letter that doesn't change?

I do this by keeping them on a USB thumb drive that I assign to drive letter B using Disk Administrator. Since I don't have floppy drives, B is always available. Windows will never choose A or B as the drive letter for inserted drives, but if you manually assign A or B to a drive, Windows will remember this and use the same drive letter on subsequent inserts of the same hardware.

Roger
+1  A: 

You need to have one volume (you can create multiple volumes on a single partition, you are not limited to 4 volumes) that is accessible from all your windows installations. This can even be a USB drive if you want, but it doesn't have to be.

You now have a few options.

Option 1: Consistent Mountpoint

Assign the same mountpoint to the common volume in all Windows installations. Lets call it G:. Then everyone can use G:\dev

This is simple (and effectively no different than the USB drive idea)

Option 2: Junction Points:

Again, assuming you have some volume that all your windows installations can see, you can use junction points.

It may be slightly tricky to set up, but it allows you to point a folder to some other location (the same way C:\documents and settings redirects to C:\users in Win7 and Vista).

Suppose each of your windows installs boots up, and sees its own volume as "C:" (but has a different letter visible from other OS installs). Also, suppose you want the folder "C:\dev" to be your source code directory on each of the windows installations.

You can create a junction point called "c:\dev" in each of your windows installations to your dev folder, wherever it is (even if its on G:).

That way, every install use the same path ("C:\dev").

Alternatively, you have:

Option 3: Virtualisation

You can create a VM to host all your dev environments, or you can create VMs to test different operating systems in. That will free up your disk configuration, and avoid test software interfering with your Windows installation(s).

Nader Shirazie
junctions work perfectly. Heres an MS app i use to help create the folder http://technet.microsoft.com/en-ca/sysinternals/bb896768.aspx
acidzombie24
Another note. I put my junction as c:\dev then put my real dev folder in c:\somePath\real_dev ATM everything works nicely
acidzombie24
the sysinternal tools are indeed fantastic. Glad that worked for you.
Nader Shirazie