Get error message cannot find SetupFixture.cs when select template in VS2017

[developersthinksmartbox]

I manually fixed it by moving the SetupFixture.cs from

C:\Users\XXXX\AppData\Local\Microsoft\VisualStudio\15.0_0adf1023\Extensions\ai1xcql0.uj3\Output\ItemTemplates\CSharp\Test\NUnit\NUnit Setup Fixture.csharp

to

C:\Users\XXXX\AppData\Local\Microsoft\VisualStudio\15.0_0adf1023\Extensions\ai1xcql0.uj3\Output\ItemTemplates\CSharp\Test\NUnit\NUnit Setup Fixture.csharp\Definitions

Applied the same fix to the other template.

[ChrisMaddock]

Something's went wonky with the packaging for VS 2017. See https://github.com/nunit/nunit-vs-templates/issues/35 - if you add the SetUpFixture from the main 'Test' part of the menu tree, rather than expanding the tree - does it work?

[rprouse]

I was told by the creator of SideWaffle which we use for the templates that they don't work properly for VS 2017 and they would not be updated because of a new way to add templates. It is likely related.

[ChrisMaddock]

New method as in dotnet new? I thought there wasn't a VS gui for that yet?

[ChrisMaddock]

Or is the suggestion that we create the files by hand instead?

[rprouse]

@ChrisMaddock I am not sure. Notice that the SideWaffle site doesn't list 2017.

According to https://github.com/ligershark/side-waffle/issues/400#issuecomment-294403742, there will be two versions of SideWaffle going forward, the 2017+ version using he new TemplateEngine that Microsoft is developing.

Full information is at ligershark/side-waffle#401

[ChrisMaddock]

Thanks Rob. Those were the threads I was thinking of - looks like there's been some important updates in the last month though.

Guess there might be a bit more work to do here, to bring this up to VS 2017.