>>Hi,
>>
>>I am beginning to work on an ASP.NET MVC 4 project with an off-shore developer. I want to be sure that when he has project ready or a progress, he can send me the solution and I can see it in my VS 2012. My question, does it matter that he creates the solution in the same letter drive as where I will be placing it? For example, I use the following convention in my VS projects:
>>
>>D:\Vs2012\WebProject\MyAppName
>>
>>As you can see that my letter drive is D: and the names are specific to my environment.
>>
>>Say he creates the project MyAppName in C:\SomeFolderName\AnotherFolderName\MyAppName. Will I have problems loading and viewing the project on my computer in my VS2012?
>>
>>TIA.
>
>Drive letters shouldn't matter but you'll both definitely want to use the same folder structure. All referenced assemblies should be contained within the same folder. For example, I've switched over to this format:
>
>Customer\GeneralProjectName\ - The generic project name (the name of the overall app.
>Customer\GeneralProjectName\NET - All .NET code for this project goes here
>Customer\GeneralProjectName\NET\Customer.Project.Assembly1 - Name of the actual .NET project
>Customer\GeneralProjectName\NET\Customer.Project.Assembly1\References - external DLL/assembly references go here
>Customer\GeneralProjectName\NET\Customer.Project.Assembly2
>Customer\GeneralProjectName\VFP - I do a lot of interop stuff so I have a different folder for each language
>Customer\GeneralProjectName\SQL - Any SQL scripts go here
>Customer\GeneralProjectName\Docs - Any docs go here
>Customer\GeneralProjectName\ThirdParty - Any third party libraries go here, but I usually copy the DLL directly into the References folder if they're needed by a specific project. I can also create a subfolder per third party tool w/their source code into this folder which makes it a lot easier to debug - I just add this project to my .NET solution and temporarily remove the reference in the "References" subfolder. You could just eliminate the "References" subfolder, but a bunch of source control utils don't really like referencing stuff "outside" of the parent folder.
>
>You basically want to be able to get a copy of the "GeneralProjectName" folder/subfolders and be able to build the app. from that. That makes source control easy and really simplifies getting a working copy of code. You don't have to hunt through 20 folders to pull together the files you need to actually compile an app.
>
>If you've got a shared source control system this becomes really easy. Just create the folder structure you want, add your code and check it all in. The other dev. can now check out to whatever drive/subfolder they want. They work in these subfolders and check in their changes. You check out any changes. It's really straightforward.

Paul, thank you very much for the detailed and helpful message.
One question I would like to ask you to clarify. When you say "shared source controls system" you mean that the entire source is in the cloud and only available via Internet connection? Also, if you do implement the shared source control system, can you still have the entire project/solution on your local drive? and use it without Internet (e.g. on a plane?)