Sitecore Support recently changed their strategy when delivering support packages. We do no longer get a patch for a specific issue - instead we get a whole package including items & files that contain all patches for our specific version so far. Cumulative patches. Sounds great.. and we just installed one on our test environment. But then came DevOps.
So we used to have all our support package file referenced into our solution - as they got included in the deploy package that worked fine locally and on our PaaS setups. All files were new compared to a vanilla Sitecore so nothing got overwritten.
In the new package, we can find dll's that will overwrite the ones from Sitecore. This is no issue when we install the package. We can transform the files from that package into a zip or deploy package that we can use in our DevOps process to PaaS to make sure it is deployed after our solution. But.. I am struggling to find a good solution for a local setup.
I can (will) install the package locally to have the items installed. But when I deploy my solution I will overwrite the support dll's again with the original ones (from Nuget). I do not want to stop using Nuget and reference the support dll's everywhere needed (that would be a recipe for disaster anyway). If there would be a way to deploy those files after my solution that would be nice - but I didn't find a good way to do that yet.
Note that the solution is Helix, with several projects.. sometimes I publish just one feature (if that is what I'm working on), sometimes I publish the whole solution.
Long story.. small question: does anyone have a good DevOps approach with the new support packages (incl local)?