This project is read-only.

Official xUnit for Silverlight repo

Topics: Silverlight test runner
Apr 6, 2011 at 3:07 PM
Edited Apr 6, 2011 at 3:08 PM Contrib could use a for managing its dependency on xUnit. Currently, I have put up my fork of xUnit with silverlight specific changes on a branch, but you could also provide yours as an "official one" and I'd be happy to remove mine. 

The advantage of using a branch is that it can either be rebased on top of xUnits default tip, but we could also merge in xUnits trunk.

Apr 7, 2011 at 9:07 PM

Yep. That's the plan. To be honest, I'd prefer not to have a separate fork of xunit, but the number of changes required are making that prohibitive. I had a quick play with subrepos recently and they look perfect for this problem. I'm currently trying to get a resharper 6 build out, and I'll get onto it after that


Apr 9, 2011 at 4:14 PM

Hi Matt,

I've played a bit with subrepos and my private mercurial hosting environment. There's basically two options for us to choose from. Either we make a reference to a public fork of xUnit that always has the silverlight fixes applied to it or we make the subrepository part of the xunitcontrib repository at the exact same location. In my private hosting, that required me to add a repository in silverlight/external/xunit that I could push to, it may be impossible to have that here at codeplex. 

Apr 9, 2011 at 4:17 PM
Edited Apr 9, 2011 at 4:25 PM

Ok, got it confirmed, it won't work on codeplex, looks like we'd need a public xunit fork. Now, there might actually be the chance of getting the xunit team to merge in our changes using the conditionals. You can see how I'd do it at