SpecFlow without code behind files (SpecFlow xUnitAdapter)

SpecFlow uses generated code-behind files for executing the scenarios. Not because we like code-behind files, but because this was the only way we could easily integrate Cucumber-style Behavior Driven Development to the .NET developer toolset. But after almost 8 years, can we get rid of the code-behind files finally? And how is it related to .NET Core? Related links: SpecFlow: http://www.specflow.org SpecFlow xUnitAdapter GitHub page: https://github.com/gasparnagy/SpecFlow.xUnitAdapter Intro blog post: http://gasparnagy.com/2017/04/specflow-without-code-behind-files/ Blog post about using assertions: http://gasparnagy.com/2016/05/specflow-tips-collect-more-information-on-error-part-2/