NodejsToolsTestDiscoverer throws Method not found: Microsoft.IO.Path.GetFileName(System.ReadOnlySpan`1)' with VS2022 17.3 about nodejstools HOT 11 CLOSED

@fforjan we'll look into it

from nodejstools.

from nodejstools.

Ping @joj and @safacero as you are the one who did recent change.
This is blocking our team to migrate to VS2022 17.3

from nodejstools.

@fforjan I'm not successful at repro'ing it! Can you share the exact steps with the exact project type and how you added the test and selected the Mocha framework? Thank you so much for your patience :)

from nodejstools.

NodejsConsoleApp2.zip

Just open the solution, wait for the tests to be discovered, check the output for the tests :

@safacero let me know if you need more info

from nodejstools.

(this was simply created by doing new project + add new mocha unit test)

from nodejstools.

@safacero also, look at https://developercommunity.visualstudio.com/t/Building-Xamarin-projects-stopped-workin/10097536#T-N10097747-N10098939 I would think this is related

from nodejstools.

@fforjan do you have C++ installed in that VS installation? If you do, can you try uninstalling "Test Adapter for Boost Test" and "Test Adapter for Google Test" in Individual Components? That issue has been fixed already, but I don't quite remember what version the fix went in. Thanks! J

from nodejstools.

@joj I will quickly check but just a remark, we are talking about the latest Visual Studio 2022 which got delivered this week. If the issue is fixed, when do you think it will be available into Visual Studio 2022 update ?

Update: the work around is working !

from nodejstools.

I checked! The change was inserted into 17.4 P1. It's already available in the Preview versions. We didn't want to ship to 17.3 because we discovered it very late in the process and when we discovered the issue, it was only affecting JS tests, for people with the C++ workload installed (so, exactly this case). We didn't think many people would be using those two at the same time, which makes the workaround fairly straightforward.

from nodejstools.

@joj thanks for following up !

from nodejstools.