Add a strong name to the LambdaTale assembly

[thomaslevesque]

Hi,

I'm trying to migrate the FakeItEasy tests from Xbehave to LambdaTale. The migration is really easy (basically just switch the package and replace using Xbehave with using LambdaTale), but I hit a snag: the Xbehave assembly was signed, but the LambdaTale assembly is not.

While strong naming is no longer useful in modern .NET, FakeItEasy still targets some older TFMs, so our tests target those frameworks too. And our test assemblies are strong-named, to be able to test some specific scenarios. On net462 and netcoreapp2.1, the LambdaTale assembly fails to load because it's not strong-named.

Would it be possible to bring back the strong name? I'm willing to send a PR for that.

[CaringDev]

Hi Thomas

Happy to hear I can contribute something... we are using FakeItEasy in many of our projects!
If you create a corresponding PR I'll merge it shortly, if not I'll do it myself by the end of next week.

Cheers, Rapha

[CaringDev]

fixed in #87 by 11053cc

[thomaslevesque]

Thanks!