Update to latest nunit

[joelmartinez]

per #246 ... which tried to make a number of changes at the same time, and resulted in some tests not passing. Let's update nunit, so that it's not a problem when we subsequently make the other project/nuget changes

[ChrisMaddock]

Great to see this issue logged. 🙂 You should be aware of @wachulski's project below, which will help with some of the heavy lifting!

https://github.com/wachulski/nunit-migrator

[joelmartinez]

Whoa, this is great @ChrisMaddock ... thanks for the heads up on this!

[ChrisMaddock]

No worries! I had a quick look at #246 and saw some of the problems you hit previously - looks like you'll need to be aware of the path changes described below:

https://github.com/nunit/docs/wiki/Breaking-Changes

I did also pull the repo to have a quick bash, but wasn't able to get a clean build - should the solution build straight out of the box in VS on Windows? Anyway...I'm all out of lunch break now! 😄

Let us know if you hit any other stumbling blocks. 🙂

[joelmartinez]

@ChrisMaddock I know this was a bit ago, but I'm going to start working on this in the next release. You mentioned you had issues building on VSWin, was it by chance similar to the issue(s) described here?
#308

[ChrisMaddock]

@joelmartinez - it was a while ago now, but yes - I had problems with the same packages. I think I also did a work around, then hit further problems, and at that point ran out of lunch break!

Good luck with the NUnit upgrade - should if we can help with anything!