Chris Maddock

Copying the below comment over here, so there's a good record. > The .NET Standard engine required to do #48 in the way we want to is actually nearly ready...

I can only repro this with a `[(OneTime)TearDown]` exception. Repro below: ``` [TestFixture] public class TestCaseSample { [OneTimeTearDown] public void OneTimeSetUp() { throw new Exception("Fails"); } [Test] public void TestAddWithResult()...

I see, thanks Charlie. We'll need to decide what we want that to look like for the xamarin runner.

One other thought - nunit-vs-templates currently packages some code snippets as well as the main templates. We'd need to work out how to approach that.

> As for snippets, if they aren't supported, then they aren't supported. From memory, I believe the current snippets are packages as a separate dll in in the same VSIX....

> Would you like to create full .NET Framework projects from command line or directly from Visual Studio? Yes - via Visual Studio is what I want to be able...

Awesome - thanks!

As a way of easing the switch, have you considered adding custom attributes/constraints for ExpectedException/throws constraint? See the nunit-c#-samples repo for an example of that.

I'd personally much prefer to see a Roslyn analyser with built in code fixes to tackle this problem, over another 2.x release - however I understand your issue, and how...

Have you tried a variety of assemblies? Doing ours - I always found the changes you've mentioned the easiest to solve - the problematic ones were filepaths/changes to make testcasesources...