[WIP][.NETCore] Removal of Code- Behind- Generation

[SabotageAndi]

#resolves #824

[gasparnagy]

@SabotageAndi What did you do in this PR exactly? It is hard to get it from the changes...

[SabotageAndi]

I integrated your PoC from https://github.com/gasparnagy/SpecFlow.xUnitAdapter into the SpecFlow solution and made changes that where needed to get the scenarios executed without codebehind file.
Next step for me was also use this for the projects that where generated and run during the tests.
If this works again, I would refactor the solution to a more generic one so that the work for other test runner is easier.

[gasparnagy]

Ah good. Did you get it working locally? (There are couple of ideas how to improve the PoC, I guess the best would be to make these improvements here. Or at least we need to sync the changes.

[SabotageAndi]

Getting it to work was not a big problem. The rest around made more headaches.

[SabotageAndi]

To continue forward with this PR, there has to be made some enhancement to the test project setup code (solution file, nuget restore, nuget feed, ...).
I wrote this already for the SpecFlow+Runner. I am working to refactor this code to make it reusable in SpecFlow & SpecFlow+Runner.

[SabotageAndi]

The test project setup code is now open sources in this repo: https://github.com/techtalk/SpecFlow.TestProjectGenerator
It should be "integrated" in this repo via subtree (https://help.github.com/articles/about-git-subtree-merges/).

The API is similar to the existing ones. So swapping it out should be not that big problem.
The added changes are written mostly for the SpecFlow+Runner tests. So it could be that there is additional work needed for other runners.

[gasparnagy]

@SabotageAndi great! (although the name SpecFlow.TestProjectGenerator is pretty confusing for me, I have to admit.)

[robertcoltheart]

What's the progress on this? Can we get this merged and released?

[SabotageAndi]

closing PR because we won't follow this idea for the first release of .NET Core support.