Running Unit Tests From Network Drive - by kswartss

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 502353 Comments
Status Closed Workarounds
Type Bug Repros 9
Opened 10/24/2009 5:10:31 PM
Access Restriction Public


When loading a test project from a network drive, Visual Studio builds the projects fine, but when running the test project Visual Studio shows the error:
"Error loading Z:\Projects\XYZ\Main\XYZ.Framework.Test\bin\Debug\XYZ.Framework.Test.dll: Could not load file or assembly 'file:///Z:\Projects\XYZ\Main\XYZ.Framework.Test\bin\Debug\XYZ.Framework.Test.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)" in the output window and does not continue.
Sign in to post a comment.
Posted by deltreey on 3/19/2013 at 2:54 PM
The workaround works great. Thanks Microsoft for not taking something this small and wasting time making a patch for it.
Posted by ABWho on 12/21/2011 at 3:42 PM
This is pretty disappointing. The bug still exists 2 years later in VS2010 SP1. All I am doing is creating a new Test Project, adding a single test and then hitting this error when I try to execute.

I've wasted 4 hours trying to find this workaround, after following a number of red herrings. And I really have no idea exactly what other side-effects the workaround might have introduced.

My guess is that there is some simple step being missed in the creation of the test project, which should be addressed. I don't appear to have problems with other types of projects I create in the same location.

Posted by Jeremy Herbison on 6/12/2010 at 7:58 PM
Really?? Won't fix?? I just spent about 2 weeks trying to find the solution to this. How about at least publishing the fix somewhere, if you're too lazy to fix it?!
Posted by bryanc on 1/16/2010 at 11:27 PM
VS Product Team:
1) you suck. this issue is a pain in the ass. "won't fix due to the easy workaround" - seriously? have you become that lazy????
2) where exactly to i set this magic setting???
Posted by Microsoft on 10/29/2009 at 1:27 PM
Hi Kevin,

With the workaround, you should be able to continue. We will close this out as Won't fix due to the easy workaround.
Visual Studio Product Team
Posted by Microsoft on 10/29/2009 at 1:27 PM
Hi Kevin,

The workaround is to set COMPLUS_LoadFromRemoteSources=1.

Visual Studio Product Team
Posted by Microsoft on 10/27/2009 at 2:10 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you