DebuggerShim.cs missing using statement for NSpec.Assertions

[BennieCopeland]

Installing the NSpec package into a new .Net 4.6.2 console application, I get an error on line 47 that 'bool' does not contain a definition for 'ShouldBeTrue' and no extension method 'ShouldBeTrue' accepting a first argument of type 'bool' could be found Adding the NSpec.Assertions namespace fixes the issue.

[amirrajan]

Thanks for the heads up. Definitely want to make sure the install process is smooth.

[BrainCrumbz]

There's an open issue, #161 , tracking a difference in what's reported in website docs and what assertions are actually available.

When you say "on line 47", which code are you referring to? Was that created out of a template, or....? Thanks for your contribution.

[amirrajan]

I updated the "hello world" code on the website. That one should work, but I still need to work through all the other ones and make sure they work with the latest version of NSpec

[BrainCrumbz]

Just inspected the sample class generated with dotnet new nspectest and that has the right using NSpec.Assertions; as well, so it should be ok.

[BrainCrumbz]

@amirrajan re. updating example code, just a reminder that with FluentAssertions for basic comparisons one can go with Should().Be(...), which might (?) look more immediate than ShouldBeEquivalentTo(...)

[BennieCopeland]

Line 47 of the debuggershim.cs file.

…

Sent from my iPhone

On Mar 20, 2017, at 21:01, BrainCrumbz ***@***.***> wrote: There's an open issue, #161 , tracking a difference in what's reported in website docs and what assertions are actually available. When you say "on line 47", which code are you referring to? Was that created out of a template, or....? Thanks for your contribution. ― You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[BrainCrumbz]

Gosh, that was right in issue title! :O Sorry for not noticing it. Thanks!