MSTest run fails because source assembly is not trusted

Question

I just added xUnit to our test project (for the Asserts, we\'re still using MSTest as the framework) and immediately the test runs refused to execute any of the tests. This

Answer 1

It's not just the moq.dll that needs to be unblocked. The latest zip file includes an moq.xml and moq.pdb file - referencing the dll copies these other two files to the bin folders as well. If all three have not been unblocked the tests won't run, I found.

Answer 2

It took me a few tries to find the answer in Google, so I'm putting it here in case anyone else runs into the same problem. A detailed description can be found at this blog posting.

Basically, the fix invovles right-clicking on the dll file (xunit.dll for example) in Windows Explorer, going to Properties, and clicking "Unblock" at the bottom of the tab next to the 'Security' text. It seems that Vista / Windows 2008 will automatically mark assemblies that come from other machines or the internet as unsafe.

As a couple commenters have mentioned, you may also need to restart Visual Studio for this to take effect.

Answer 3

It may seem really obvious now, but when I was clicking unblock the file was set as read-only.

Only after un-checking that attribute, applying, then selecting unblock did I actually get this working.

Give that a go.

:)

PS: I also deleted all the old dll's in my bin folder, just to make sure Visual Studio wasn't picking up the old one.

Answer 4

• Go to file
• Right click and select Properties
• On the first Register click on Allow