Skip to content

“Failed to Start Monitoring Changes” Error in VMWare Fusion

My day job requires me to use both Perl and C#. My prefered development environment is on my Macbook. When hacking Perl, I use TextMate, but for my C# work, I need to use Visual Studio. Luckily, VMWare Fusion lets me run the dreaded Micro$oft IDE when I need it. Since our source code is all in a Subversion repository, and since I already checked out my code on the Mac, I thought why not just open and edit my Visual Studio solutions off of the shared network folder that Fusion creates? That way, I can run Visual Studio in Unity mode and use the command-line Subversion tools in Terminal.app. However, this has not worked out as I had hoped.

Creating a mapped drive letter to my networked volume is easy. I have read/write access to the files on my Mac via this networked volume. But, I encounter two problems.

First, when trying to open a Solution file within Vistual Studio 2005 that is stored on a network volume, it will give me this error about the project location being untrusted:

Visual Studio 2005 untrusted location error

Now, this error is easily banished with a simple caspol invocation on the command line:

caspol -m -ag 1.2 -url urlname FullTrust

Just replace “urlname” with the full UNC path as in “\\\\Some\\Path\\*” and remember to include the “*” at the end.

The real problem I am having is when I try to run a project. It compiles just fine, the ASP.NET Development Server starts up, and my Web browser opens up trying to load the .aspx page. But, I always get a server error message that says “failed to start monitoring changes…” like this:

Failed to start monitoring changes error

If I use TortiseSVN to check-out the files directly onto the virtual hard drive, everything works without incident. I’d really prefer to avoid duplicating files on the virtual hard drive, if I can help it. Does anyone out there in Blogging Land have a solution to this issue or even know exactly what is causing it?

{ 2 } Comments

  1. Dave | February 28, 2008 at 7:47 pm | Permalink

    did you ever find the solution?

  2. Stephen Tolton | February 28, 2008 at 7:51 pm | Permalink

    No, I didn’t find a solution. I just installed VS2008, so I’ll see if the error persists there. But, it might be related to the OS (WinXP) or the version of IIS running or something else. I’ll post an update after I try it again with VS2008.

Post a Comment

Your email is never published nor shared. Required fields are marked *