@byteblast this is good to go if you are happy. I modified the CI environment to run all the tests.

After this gets merged we have:

• TestStack.FluentMVCTesting
• TestStack.FluentMVCTesting.Mvc4
• TestStack.FluentMVCTesting.Mvc3

And the dlls in all three get tested by the tests every build.

When deving you can ignore the OldMvc projects since they automatically include everything in the main project. The only implication of how I've done it is if we add a new file or delete a file then you need to unload and reload the projects since they load which files are included when the project is opened.

I made an empty MVC 4 project and then referenced the respective FMT assembly and got this error.

I am not at all sure, but would would it perhaps make sense to reduce the target framework version accordingly?

It may also be a good time to update the readme to reflect the new package arrangement?

Otherwise it looks great bud 🍻

Oops. I'll need to fix that - thanks for testing it. Will get back to you when it's sorted.

On 21 Sep 2014, at 1:26 pm, ByteBlast notifications@github.com wrote:

I made an empty MVC 4 project and then referenced the respective FMT assembly and got this error.

I am not at all sure, but would would it perhaps make sense to reduce the target framework version accordingly?

It may also be a good time to update the readme to reflect the new package arrangement?

Otherwise it looks great bud

—
Reply to this email directly or view it on GitHub.

Give it a go now :)

also, FYI you can log into the CI server to get the built nuget packages. For this pull request it's at: http://ci.robdmoore.id.au:8010/viewType.html?buildTypeId=TestStackFluentMVCTesting_CI&branch_TestStackFluentMVCTesting=35&tab=buildTypeStatusDiv. Just clikc login as guest and you can see the builds and download the artifacts.

Awesome.