Visual Studio Project in Shared Folder

[Danmoov2]

This could well be a VS issue I can't solve and might be totally unrelated to Fusion if so apologies but i've not had much luck elsewhere.

I've just setup Visual Studio 2008 on Vista through Fusion on OSX 10.5.5. I want my VS projects folder to be in my OSX Docs folder not on a virtual disk within the VM so I can maintain a consitent folder setup and this will work better with my backup seutp. My only issue is not being able to get the share/permissions setup properly to ensure that VS has the appropriate trust setup on that folder.

I've tried running caspol and the config setup tool as I detail in this post.

Whenever I try to build an ASP.Net app I receive the error:

Failed to start monitoring changes to V:\vs projects folder\some project\

Where V: is a mapped network drive to a share on
.host

If anyone has resovled this I'd be hugely thankful :S

Cheers

[WoodyZ]

This is probably an issue involving the VMware Shared Folders feature in that it use a "." (dor or period) as in ".host" as the first character in its name. This has been a known issue with various programs over the years and the best solution is to not use the VMware Shared Folders feature with the program that can't handle a path that has a "." as the first character in its name and try using a SMB Share setup in OS X and then map to that share in Windows.

[borisdusek]

Did you try caspol in the "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727" folder? (that's the correct one). Also the commands listed in the post you linked differ a bit from the commands I found on this Microsoft-employee blogpost. I also read the with .NET 3.5 SP1, there is no longer need to set trust on shared folders, perhaps you could try to install VS2008 SP1 (I think it includes .NET 3.5 SP1) if you want to try it.

[Danmoov2]

I believe it's something to do with OSX folders not using the same notifications as windows. I'm pretty sure I've done all I can with caspol (used the v2.0xxx folder). Have also tried SP1. Begining to think I'll just have to make do with the virtual disk

[ewoo]

It seems that there's a workaround!

This means that to make the .NET framework trust your VMWare shared
folder, you have to add the path to the “Internet_Zone”. Not the
“LocalIntranet_Zone”, because the framework loader doesn’t even look
there.
Once I’ve changed that configuration, Visual Studio complained that
it was unable to parse the host name - it seems to assume them not
starting with a dot.
This was fixed by mapping the path to a drive letter like we did centuries ago.

[KingTuck]

Sorry, I'm a little confused by the blog post.. when you say you're adding the path (I'm assuming just something like
.host\Shared Folders\Projects) what application are you using? And once in that application, where do you add the path? Maybe some screenshots or a step by step would be helpful.

Thanks!

[sodapop]

I just had this problem and looked all around for a fix that allowed me to keep using the Shared Folders feature of Fusion. I didn't find anything. But I did cobble together a workaround and figured someone else might benefit.

I wanted to use Fusion to host Vista, so I could do development work in Visual Studio 2008. I liked the idea of using shared folders so that I could store all my project files on my mac. The main reason being I wanted to allow Time Machine to back these files up without backing up the huge virtual machine image. I tried all sorts of things, mostly revolving around mapped drives and the .NET Framework configuration tool, and nothing worked. So I bailed and went a different route.

Based on some googling, I decided to enable windows file sharing on the mac, sharing my $username$ folder via System Preferences > Sharing. On the VM, I mapped a drive to this shared folder using drive Z:\ and mapping to
10.0.1.200\$username$. I added connection credentials by clicking the link in the Map Network Drive window, specifying the user name (like so: WORKGROUP\$username$) and password of my mac user account. Finally, I added the mapped drive as a full trust site using the .NET Framework configuration tool, adding a machine code group security policy for the Internet_Zone for the mapped drive. This did the trick.

Sorry for the rather undetailed description. I figure most people who may have a problem here have messed around with everything I've mentioned. But if not, fire away.