Posted 9 December 2020, 8:09 am ESTWe maintain many different applications that share core libraries, including a shared library with common functions for AR reports. It was easy to sync AR versions between the core library and inheriting apps until AR 14 because of the Nuget updates.
Now, it takes a lot of effort to keep inheriting app projects in sync with our core AR library (using VS 2019) because;
1. there are many, many AR packages
2. the packages are frequently updated, and
3. trying to 'update all packages' never completes without failing on a dependency somewhere.
Also, when an inheriting app needs to be updated to match the core AR library so it will compile, the AR packages for the app have to be updated to match the core AR library references rather than the latest AR packages. Otherwise, if we update the app to the latest packages, the core AR library becomes outdated and the whole cycle starts over again.
As a result, doing piece-meal updates of every inheriting app project any time we update our core AR library is taking way more time than it should and can literally waste hours of time for updates that don't usually change anything in our app's reports.
1. Is there a quick way to update AR to specific versions of each package? Perhaps a script for the Nuget package manager console rather than the Package Manager UI?
2. Is it possible to reduce the number of packages in future releases of AR? It seems like most/all get installed when doing even a basic report anyway. This would also reduce assembly binding redirects for AR, of which there are almost 30 now in our app web.config files.