bgeihsgt;6989 wrote:Thanks Remco. Running against the bleeding edge of xUnit is important to our team because Brad Wilson is on our team :P I guess I'll just wait until the next build of NCrunch comes with a stable release of xUnit. Should I say anything to Brad relating to this (i.e. should I tell him not to move the code to a different assembly because it breaks your integration?)
That is the single best excuse for bleeding edge adoption I've heard .. well.. ever :)
I'm happy with discuss options with Brad if he feels a little cornered by this. I think he was talking earlier about RC2 of xUnit V2 being ready soon, so this would be a good milestone to realign NCrunch with. As soon as RC2 is locked off, I should be able to get your team an early build without needing a full NCrunch release behind it. My big fear right now is that if I integrate with a new dev build of xUnit, it will break the integration for users running older versions... If we can avoid this, then I think the change can be accommodated.