There are some additional packages that get added to packages.lock.json files when you do dotnet build -c Release as opposed to dotnet build. This change adds the release package updates to the lock files. I also removed the architecture-specific sections that got added to the lock files in our end-to-end test projects, just to cut down on noise. Those sections don't appear at all unless you do dotnet publish -r <rid>, and the last rid always wins.
To test, I confirmed the Build CI pipeline passes.
Azure IoT Edge PR checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
There are some additional packages that get added to packages.lock.json files when you do
dotnet build -c Releaseas opposed todotnet build. This change adds the release package updates to the lock files. I also removed the architecture-specific sections that got added to the lock files in our end-to-end test projects, just to cut down on noise. Those sections don't appear at all unless you dodotnet publish -r <rid>, and the last rid always wins.To test, I confirmed the Build CI pipeline passes.
Azure IoT Edge PR checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines and Best Practices
Testing Guidelines