Team System Developer Center > Visual Studio Team System Forums > Visual Studio Team System - Testing > Test Run deployment issue: The location of the file or directory <assembly path> is not trusted.
Ask a questionAsk a question
 

AnswerTest Run deployment issue: The location of the file or directory <assembly path> is not trusted.

  • Tuesday, September 27, 2005 5:25 PMMichael Miller Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I am getting this error when I try to run a unit test.  The assembly is a 1.1 assembly that is strong named.  What else do I need to do? 

Answers

  • Tuesday, September 27, 2005 6:02 PMdhopton MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    For this you need to trust path the assembly is from.

    This can be done through the .net configuration wizard -- Just add that specific path as full trust, and you should be fine.

All Replies

  • Tuesday, September 27, 2005 6:02 PMdhopton MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    For this you need to trust path the assembly is from.

    This can be done through the .net configuration wizard -- Just add that specific path as full trust, and you should be fine.
  • Tuesday, September 27, 2005 6:22 PMMichael Miller Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks for the reply - but I think it was another problem.  I checked the .NET configuration settings and by default the My_Computer_Zone covers the location of the assembly with the FullTrust permission set.  The problem appears to be that the referenced assembly had a security attribute set and when viewing the properties of the file I saw the following message: This file came from another computer and might be blocked...  I clicked the Unblock button, rebuilt and it worked.  Thanks for the help.
  • Friday, October 28, 2005 12:20 AMJames Fuhr Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Is there a way to prevent Windows from re-blocking an assembly after you unblock and rebuild?

    I unblocked the assembly, rechecked properties, then rebuilt.  After a rebuild, the assembly is once again blocked.

  • Friday, October 28, 2005 12:26 AMJames Fuhr Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Big SmileAh, I figured out what I was doing wrong.

    I was unblocking the copied assembly and not the source assembly.

    Once I unblocked the assembly at the source location, the copied version into the bin directory was fine.
  • Friday, July 13, 2007 12:34 PMsoundman32 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    My system (XP/SP2) doesn't have an unblock button !!

    Is there another way of unblocking this?

    Neil

  • Monday, December 08, 2008 5:02 PMDevdumper Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals