After the CPM switch with the backend services repo, this repo also needs Directory.Packages.props to build within this repo.
Need to think about best practices with such a scenario. It's not the same Directory.Packages.props needed as with the backend services.
In the same topic list, how is the common services library dealt with? Might create a common nuget package.
After the CPM switch with the backend services repo, this repo also needs Directory.Packages.props to build within this repo.
Need to think about best practices with such a scenario. It's not the same Directory.Packages.props needed as with the backend services.
In the same topic list, how is the common services library dealt with? Might create a common nuget package.