I found the support for switch-to-projects/packages for packages built from multiple projects, added by @MaartenBE in #27, useful however it would have been nice if had been documented, so I've updated the documentation in the README to cover it, using the same OPCFoundation.NetStandard.Opc.Ua package as tested against (the package I needed it for is not open source) with a sample solution name in the example switcher.json JSON.
Also: I haven't changed the wording but I'm not sure what the sentence "The involved projects are only specified by the solution path in the settings file" is meant to mean exactly. Is it trying to say that the project paths are relative to the solution file specified? Is "settings file" the switcher.json file? Or am I being stupid?
RicoSuter
commented
3 years ago
I found the support for switch-to-projects/packages for packages built from multiple projects, added by @MaartenBE in #27, useful however it would have been nice if had been documented, so I've updated the documentation in the README to cover it, using the same OPCFoundation.NetStandard.Opc.Ua package as tested against (the package I needed it for is not open source) with a sample solution name in the example
switcher.jsonJSON.Also: I haven't changed the wording but I'm not sure what the sentence "The involved projects are only specified by the solution path in the settings file" is meant to mean exactly. Is it trying to say that the project paths are relative to the solution file specified? Is "settings file" the
switcher.jsonfile? Or am I being stupid?