Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I managed to get hold of Jeff Wilcox (the author). He said, 'it isn't packaged with the toolkit, it's separate. I believe some community folks packaged it up but i haven't released it on nuget unfortunately, sorry!' </p> <p>No problem. Well thanks Jeff for making it available in the first place. What's an extra hoop to jump through to a developer anyway. That'll teach me for making too many assumptions ;-).</p> <hr> <p><strong>previous update</strong></p> <p>went to [silverlight.codeplex.com] <a href="http://silverlight.codeplex.com/SourceControl/list/changesets" rel="nofollow">http://silverlight.codeplex.com/SourceControl/list/changesets</a> and downloaded the latest source code. I discovered that Jeff Wilcox is still updating the testing .dll (last change back in Feb).</p> <p>So I'm digging through the source code. Took a while to find unit.testing.csproj under .\SLToolKit\Silverlight4\Infrastructure </p> <p>Found that there's a dependency on Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight</p> <p>I'm guessing that this .dll is part of any of the Visual Studios greater than professional. Am I wrong?</p> <p>Even though the sourcecode is kept in the SilverlightToolkit, the Microsoft.Silverlight.Testing.dll to my knowledge isn't shipped with any of the NuGet downloads. I wonder why? Getting closer at least.</p> <hr> <p>Giving up on where the .dll comes from for now (still curious though), and am taking the versions from .\Silverlight4\Source\Binaries that came with the source code instead.</p> <hr> <p>Awesome: Resharper picked it right up with those little circle things over on the left margin.</p> <p>Did I just answer my own question?</p> <pre><code>using System; using Microsoft.VisualStudio.TestTools.UnitTesting; namespace a_namespace { [TestClass] public class Class1 { [TestMethod] public void test() { Console.WriteLine("test"); } } } </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload