Split Engine Extensions into separarate projects about nunit-console

[rprouse]

I created issue #67 for this and put it in the milestone so it will be included in the upcoming release. It is an easy fix, we just need to decide on the wording. If you have ideas or suggestions @aateeque, please head over to #67 and give us your feedback 😉

[CharliePoole]

@nunit/core-team @NikolayPianikov

Before moving ahead on this, I'd like to collect your ideas about any lessons learned from having separated the teamcity extension. My own thoughts include:

• Make sure we have unit tests.
• Extension should include integration tests that use the latest console/engine release
• Console/engine should include integration tests that use the latest extension releases and run them before packaging.

Your thoughts?

Next step will be to pick the next extension to unbundle.

[CharliePoole]

@nunit/core-team @NikolayPianikov
No comments guys? I'm moving ahead then.

[CharliePoole]

I'm removing extensions from the nunit-console project one at a time. As I remove them, the console package still has dependencies on them and assumes that their version is the same as that of the console. That won't always be true. The final step in completing this issue after all the extensions are removed will be to determine how we will maintain a list of the versions to use for package dependencies.

[aateeque]

@CharliePoole looks like the nuget package NUnit.ConsoleRunner.3.4.1 went from one bringing all the extensions to now being being one without extensions in the same version of the package. Is this true?

[rprouse]

@aateeque if you look back through the versions of NUnit.ConsoleRunner, you will see that it never had dependencies and I don't think it ever included the extensions. The one you want is NUnit.Console, https://www.nuget.org/packages/NUnit.Console/

@CharliePoole I wonder if we should update the description of NUnit.ConsoleRunner to let people know it is probably not the version they want. We get way too many issues reported around this. I am going to create an issue for the 3.5 release to update the wording in the NuGet package.

[aateeque]

@rprouse spot on, NUnit.Console is the one I want. I think at one point the past couple of weeks NUnit.ConsoleRunner had dependencies; because I setup a project with it. But then this week they silently seemed to have disappeared, which was quite frustrating for our team. Updating the descriptions would be great help