I have to say I wish you hadn't used this unsupported immature framework in your tests.
Not only do your examples force people to use this nbehave framework, you can't even get it out of nuget in a useable form any longer. It also seriously diverged from the idea of TDD and went straight to BDD. For no reason.

It would be nice if you could post a workaround example based on one of your test setups that does not depend on NBehave. Its extremely tedious now trying to get your examples to work because you essentially have to download your sample code to get the frameworks you are using instead of just using package manager.

It also means it is code that would never be used in a production environment.

Ibviously we all will be having the same problem. Initially I downloaded the NBehave Nuget package and found, as JAD has, that the nuget package does not resemble the libraries used by the authors.

The business friendly naming convention can be adopted almost the same without using NBehave. I get a bit annoyed by books that take the reader down the route of using specific non-standard frameworks when teaching the raw principles would be more benificial in the long term.

It looks like nbehave has moved from this way of working into gherkin. I'm guessing that I should uninstall the nbehave nuget package and grab the 0.2.6 version of nbehave to continue working through this. Kindle Book needs updating