This was just a first attempt at checking off a personal backlog item through refactoring. We've used Shouldly over Should for a while now. It's more frequently maintained, and provides nicer error messages. I split out the Should extensions from the Autofac and Structuremap assemblies and made them into their own independent SpecsFor.Should, and then added similar items for Shouldly. I'm sure some of this could be refactored back into Core, since large parts of it don't actually reference either library, but I thought this was a good first "thing" to work on.
I added a pretty standard editorconfig file to lock down coding styles for the project. It's just lifted from other current projects of mine, and may not match your styles 100%, but it's a start.
I updated package references that were at least "in range". The demo project is still referencing SpecsFor v6.0.0, but it's the full release now instead of the alpha. I'd update it to 7, but that requires some rewriting. Autofac.Extras.Moq has jumped from 4.2 to 6.0, so I left that one alone for now as well. Two whole point releases seems dangerous to me. Maybe I'll swing back around to this later on. Everything else was at most a minor release or two, and seems to have updated without any issue. That's no guarantee of compatibility, but all the tests pass.
I have no clue about building NuGet packages, but I took a stab at it based on what was already there. It's probably all wrong, but I'd like to learn.
This was just a first attempt at checking off a personal backlog item through refactoring. We've used Shouldly over Should for a while now. It's more frequently maintained, and provides nicer error messages. I split out the Should extensions from the Autofac and Structuremap assemblies and made them into their own independent SpecsFor.Should, and then added similar items for Shouldly. I'm sure some of this could be refactored back into Core, since large parts of it don't actually reference either library, but I thought this was a good first "thing" to work on.
I added a pretty standard editorconfig file to lock down coding styles for the project. It's just lifted from other current projects of mine, and may not match your styles 100%, but it's a start.
I updated package references that were at least "in range". The demo project is still referencing SpecsFor v6.0.0, but it's the full release now instead of the alpha. I'd update it to 7, but that requires some rewriting. Autofac.Extras.Moq has jumped from 4.2 to 6.0, so I left that one alone for now as well. Two whole point releases seems dangerous to me. Maybe I'll swing back around to this later on. Everything else was at most a minor release or two, and seems to have updated without any issue. That's no guarantee of compatibility, but all the tests pass.
I have no clue about building NuGet packages, but I took a stab at it based on what was already there. It's probably all wrong, but I'd like to learn.