Playwright template content overwriting default template in VS 17.12.0 Preview 4?

[michael-hawker]

Poking around the template configs in main, I can't see how this is happening; as there are two separate templates, the default one and the playwright one.

But in VS 17.12.0 Preview 4, I see a weird amalgamation of the two templates:

This has the default template's name and description, but the playwright tags and CONTENT... (the content being incorrect is the big issue here as it makes it hard to just get started with a basic .NET unit test.) It the only basic 'MSTest' template I see.

Compared to VS 17.11.5 (which still works as expected):

Is this a known issue with VS preview? Is there a way I can tell it to grab the latest feed with this repos content to get the basic blank template?

I need to use VS Preview for a .NET Conf demo recording (on 10/30), but we need to create the basic Unit Test template...

[michael-hawker]

Update here, I updated to Preview 5 and saw the same issue. However, if I completely uninstalled VS Preview and then re-installed it, then I got more templates back finally.

However, the Playwright template still should as having the wrong name, and they both don't have the test beaker icon as one would expect:

Selecting the first template works as expected for the content generated. So, still not quite sure what's going on here.

I had someone else who had Preview 3 look at what they had, and they saw a similar result as I see on a fresh install above:

I installed only the following workloads:

I:\code>dotnet --version
9.0.100-rc.2.24474.11
 
I:\code>dotnet --list-sdks
8.0.403 [C:\Program Files\dotnet\sdk]
9.0.100-rc.2.24474.11 [C:\Program Files\dotnet\sdk]

And then I also have VS 17.11.5 installed as my stable build of VS.

[Evangelink]

I have checked on 4 different machines and it's working fine for all of them so not sure what's going on.

[michael-hawker]

@Evangelink were those fresh installs or updates? Wonder if it's an in-place upgrade issue vs. fresh install? As I did see improvements when I uninstalled the preview vs. updating/restore.

[Evangelink]

I need to double check but it was most likely mainly updates and not fresh install. Although we had some vendors validation on that scenario too.