>>>>Thank you. I will keep the referencing assemblies in mind when importing the project.
>>>>
>>>>>It might make a difference for referencing assemblies. But you should only have to delete the reference, then add it again.
>>>>>
>>>>>>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.
>>>
>>>Or you can use the free online TFS and then it won't matter..... You just get latest...
>>
>>Thank you. I thought about it but decided that I prefer a simpler approach (for me).
>
>Working w/o source/version control is like driving blind.
>
>Even for a single developer, source/version control is absolutely mandatory IMHO.
My "issue" with TFS was not source/version control but the fact that is "online"
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham