I am taking the Quickstarts Commanding as an example.

1. Build Commanding.sln

a. silverlightut binaries

Symptom - you may get heaps of compilation errors. Here is one example:

…\CAL\Silverlight\Composite.Presentation.Tests\App.xaml.cs(19,17): error CS0234: The type or namespace name 'Silverlight' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)

Cause – The referenced Microsoft.Silverlight.Testing.dll & Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight.dll are missing

Solution – Download the “Silverlightut” (Silverlight Unit test framework) from http://code.msdn.microsoft.com/silverlightut | Extract the two dlls to LIB\Silverlight\UnitTestFramework | Restart VS IDE 

b. ValidateXaml

Symptom – You may get the following error:

Cause – No clue except the VS installation is possibly messed up somewhere.

Solution – Upload the project file | Modify ValidateXaml node from true to false | Save changes & Reload the project

2. Build Commanding.Tests.AcceptanceTest.sln

a. white binaries

Symptom – you may get heaps of compilation errors. Here is an example:

…\AcceptanceTestLibrary\AcceptanceTestLibrary\ApplicationHelper\WhiteExtensions.cs(21,7): error CS0246: The type or namespace name 'Core' could not be found (are you missing a using directive or an assembly reference?)

Cause – The referenced Core.dll & Bricks.dll are missing

Solution – Download the “White Binaries” from http://www.codeplex.com/white  | Extract to LIB\White

b. project hint path

Symptom – you may still get heaps of compilation errors similar to 2a

Cause – The Commanding.Tests.AcceptanceTest.csproj has incorrect hint path for Core.dll & Bricks.dll

Solution – Unload the project file | Mofiy the HintPath from \LIB\Core.dll to \LIB\White\Core.dll | Modify the HintPath from \LIB\Bricks.dll to \LIB\White\Bricks.dll | Reload the project file | Restart the VS IDE

3. Test Commanding.Tests.AcceptanceTest

a. Test run error

Symptom – You may get the Test Run Errors and Warnings

Failed to queue test run '…': Test Run deployment issue: The location of the file or directory '...\quickstarts\commanding\commanding.tests.acceptancetest\commanding.tests.acceptancetest\bin\debug\Core.dll' is not trusted

Cause – As the error message correctly indicates, we need to trust the referenced White assemblies.

Solution – Open \LIB\White\Core.dll properties | Unblock & Apply/OK | Rebuild Commanding.Tests.AcceptanceTest.sln

Note – Make sure you are unblocking the assemblies in the LIB not the bin\debug.

b. Test run failed

Symptom – You may get the error message:

System.IO.FileNotFoundException: Could not load file or assembly 'Castle.Core, Version=1.0.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' or one of its dependencies

Cause – The depending White assemblies are missing

Solution – Make sure the following assemblies are under \LIB\White

• Bricks.RuntimeFramework
• Castle.Core
• Castle.DynamicProxy2
• log4net
• nunit.framework
• White.NUnit
• Xstream.Core

Note – If you click the “Test run failed” link, the “Test Run Errors and Warnings” actually listed all the missing assemblies.

Note2 – Make sure you unblock the above assemblies as well.