However, there are many that use Visual C# Express 2010 without problems on Win8 (that doesn’t make it any more supported though).
There are known issues however with macs and virtualisation, although I can’t remember the details as to whether Parallels was explicitly called out as bad… from memory, bootcamp is the only way reliably to have that work; I’d suggest a quick search here on the forum for background. But the behaviour was about issues with USB and deploying, not directories - can you please tell us what you were attempting to do when you generated that error?
@ SpiderCred - This error usually means (well in my experience) that there is an intermediate file in build process that stuck and prevents the build process to finish.
Try closing the solution and delete bin and obj folders inside the project folder. Open the solution again and rebuild everything.
The test I would always try is create a new project, drag a mainboard and a module to the designer, then deploy the code. If that works, there’s something wacky with the old project, so copy your code into the new project shell and see if that helps - if the fault comes back then it might have come with your code. Reduce what you bring over and keep trying to identify what.
Ok in that command prompt navigate to the folder where your solution is located. Once there run the following command: msbuild “your solution .sln file”