Guess I can delay it and switch to macos-15-intel for now.

This probably needs to be a major version bump because that runtime is also included in the AnyCPU versions of the library. And that will also allow me to add the breaking changes that I have been saving up here: github.com/dlemstra/Mag....

Thanks for offering to help. I created this ticket: developercommunity.visualstudio.com/t/Usability-.... Also found out it only seems to happen when I set the filter. When executing the unit test through "all tests" it directly shows me the result.

Will still open a ticket about this. Because I still need to click it to see the error message and it should also work at different depth levels.

I really did not forget this.. I need to click the tree open each time to see the error. This does not happen with a successful unit test. While writing you this message it seems to be related to the depth but only with error. Changing group by to State "fixes" this because there are only two levels

I use it to distribute a library with C# and native code that works on Linux (glib and musl), macOS and Windows in a single @nuget.org package.

Not yet. Will create one this weekend then. Thought you might already know the answer 😁

My brain read subtle instead of subtitle and disagreed.

I moved everything to a @github.com pipeline: github.com/dlemstra/Mag.... This uses @dot.net sign to sign it with trusted signing (azure.microsoft.com/en-us/produc...). And a super easy to use action to publish the web app in #azure (github.com/Azure/webapp...)

No worries that's the disadvantage of text. No offense taken.

As I said I can completely understand why. I just did some extra testing to see if I could break it differently and it does report an error when I do this:

Artifacts\bin\a.xml = Artifacts\bin\b.xml

The good news is that I cannot break copilot or search with a valid file.

One of the issues is now closed as a "not a bug". I can understand the reason why. It would still be nice if @visualstudio.com would report an error when a solution file is malformed.

We still support VS2017 and it feels that the slnx is not actively pushed to users? And is that even supported for c/c++ projects?