I am planning to distribute this adapter internally as a nuget package. It doesn't seem you had nuget support configured in this repository, so I set it up. It took quite a lot of head banging to figure out how to convince nuget to install a package consisting of managed assemblies to a native project, so I thought I'd share my configuration in case you want to set up official nuget packages some day.
End assembly file name in .TestAdapter to make VS recognize it from a nuget package.
Create Catch2TestAdapter.nuspec to configure the nuget package. I tried embedding the nuget metadata in the project, but could not get it to support the exotic combination of having .NET assemblies that are meant to be installed in a native project.
I am planning to distribute this adapter internally as a nuget package. It doesn't seem you had nuget support configured in this repository, so I set it up. It took quite a lot of head banging to figure out how to convince nuget to install a package consisting of managed assemblies to a native project, so I thought I'd share my configuration in case you want to set up official nuget packages some day.
.TestAdapterto make VS recognize it from a nuget package.Catch2TestAdapter.nuspecto configure the nuget package. I tried embedding the nuget metadata in the project, but could not get it to support the exotic combination of having .NET assemblies that are meant to be installed in a native project.See https://github.com/microsoft/vstest/blob/main/docs/RFCs/0004-Adapter-Extensibility.md
Command to generate the package:
nuget pack Catch2.TestAdapter.nuspec -Version 1.8.0 -p Configuration=DebugPS. For
.vcxprojs VS only finds adapters mentioned in packages.config, not inPackageReferences, unless you apply extra invocations.