Running Visual Studio with code files on the Mac shared drive

[joe.bruce]

Hi,

I'm trying to develop a website in Visual Studio on an XP virtual machine and the code is on the Mac shared folder (which looks like a network folder to XP). VS reports security errors when loading a project (the code is not fully trusted) and monitoring errors when trying to run ('Failed to start monitoring project x'). To fix the security issue, I tried what microsoft suggests for granting Full Trust to local intranet filesystems, but that did not solve the problem. For the run errors, I have no clue how to tackle the problem.

My hope is that someone else has tried to do this, encountered the problem, and solved it. Currently I have the code in the vm filesystem, and it works fine. But the ideal situation would be to have the code in my mac Documents folder (or something similar).

Thanks.

 

[John@Parallels]

http://www.acthompson.net/DotNet/setting_a_trusted_location.htm

 

[joe.bruce]

Thanks John. Those instructions are the same as those provided by Microsoft (http://msdn.microsoft.com/en-us/library/zdc263t0(VS.80).aspx). I have followed those already, to no avail.

 

[fbronner]

You could try setting up CVS server on your mac, then using tortoisecvs on the windows side to checkin/checkout the code coming from the mac.

That would work.

 

[joe.bruce]

That would work, but it's a very similar solution to keeping files local to the vm, which I'd like to avoid.

 

[fbronner]

No, it is completely different in the sense that the files would reside on the MAC OS X, they would be backed by time machine assuming you are using it.

 

[fbronner]

By the way, you would not even have a shared folders set up or accessed using that solution.

 

[joe.bruce]

I must misunderstand your idea. The cvs server is on the mac, and the files managed by the server are on the mac. I understand that part. But for the vm, it has to pull down a local copy from the cvs repository and then submit changes in turn. So I still have a local copy, with the added overhead of synchronizing. Is this what you're proposing?

 

[fbronner]

I must misunderstand your idea. The cvs server is on the mac, and the files managed by the server are on the mac. I understand that part. But for the vm, it has to pull down a local copy from the cvs repository and then submit changes in turn. So I still have a local copy, with the added overhead of synchronizing. Is this what you're proposing?

Yes, I know it means you have 2 copies of the source code which means you loose some space, but you can checkout your code in the morning, and it gives you the possibility to rollback if you make a major mistake, or start new trunks if you want to explore new ideas.