The new boot from vhd feature that shipped in Windows 7 and Server 2008 has now given developers new options for setting up a test systems with different versions of Visual Studio.
For the purpose of this post, local system is the vhd boot volume and host system is the operating system and its drives that the vhd is physically located on.
Some developers are booting into their vhd, then accessing source projects that are actually located on the host system or are trying to load projects located on the network.
We recommend that projects be located on the local system. However, if your scenario requires that you load projects not located on the local system, the following steps can be taken to enable this scenario.
If you must use a project on a network share, map the network share to a local drive rather than trying to use UNC path similar to the below example.
Example: Map \\systemName\pathName to e:\shareName.
The loadFromRemoteSources option is available to enable assemblies being loaded from remote sources to be loaded as full trust.
Please ensure that you read the MSDN loadFromRemoteSources topic and are fully aware of the implications of using this setting. The MSDN topic has instructions for enabling this setting.
If you have Visual Studio 2010 installed on a vhd, and your source projects are located on the host system or network drive, you’ll need to use the loadFromRemoteSources setting to enable this scenario.
Microsoft values your opinion about our products and documentation. In addition to your general feedback it is very helpful to understand:
- How the above features enable your workflow
- What is missing from the above feature that would be helpful to you
Thank you for your feedback and have a great day,
Visual Studio Cider Team