so I am in a position where I doubt my solution to the following problem: - we are developing a wpf desktop application with c# and have a decent plugin system. This increases the libraries we have in the system (multiple git repositories, multiple libraries). The libraries are then packaged to our local nuget server. The problem is that we need to upgrade version and call nuget package even for local builds & tests. in the end a library could have 100 version numbers before a feature is done.
I have come up with an idea that we would have 2 different nuget servers. one for release builds of the libraries and one for debug builds. The problem would be though that the debug versions would be much higher than the release builds. This could be done with jenkins release build of the complete system but it would increase the release time astronomically because the main project needs to register these libraries (services) by referencing them with a version.
the libraries itself have dependencies with other libraries or private libraries and then they are registered with an IoC container. This gives us an extreme advantage. I dont want to lose this flexibility as our system is extremely customizable.
so my question is for you guys: how do you handle this dilemma ? how do you work with hundreds of libraries (Services) and their debug & release builds ?