** Issue: Code Maintenace is overwhelming.
The original Identity Server 4 samples, including Quickstarts, KeyManagement and Clients, use lots of repetitive code. Code base changes to the main solution projects require the updates to be merged into the sample projects. The sample projects then need to be pushed to separate Templates and Quickstarts repositories. Then the documentation for the main code base, the samples, the quick starts need to be upgraded, as well as their copies in the external repositories.
There are nearly 80 projects in the main repository, many of which are exact copies, such as the API, MVC and IdentityServer project in each of the QuickStart and Client Samples.
Solution you'd like
[ ] Upgrade top-level statements to reduce size of codebase
[ ] Consolidate namespaces into global usings to reduce size of codebase
[ ] Remove client-side libraries from source and use LibMan to restore on build to reduce maintenance and keep packages patched and up to date.
[ ] Consolidate samples, templates and quick start to use shared API, MVC and Identity Server projects. This task can be moved to the next milestone.
Alternatives
Continue to manually make changes to the main code based and then manually sync changes to each of the many samples, quickstarts, templates and manually update their documentation.
** Issue: Code Maintenace is overwhelming. The original Identity Server 4 samples, including Quickstarts, KeyManagement and Clients, use lots of repetitive code. Code base changes to the main solution projects require the updates to be merged into the sample projects. The sample projects then need to be pushed to separate Templates and Quickstarts repositories. Then the documentation for the main code base, the samples, the quick starts need to be upgraded, as well as their copies in the external repositories.
There are nearly 80 projects in the main repository, many of which are exact copies, such as the API, MVC and IdentityServer project in each of the QuickStart and Client Samples.
Solution you'd like
Alternatives Continue to manually make changes to the main code based and then manually sync changes to each of the many samples, quickstarts, templates and manually update their documentation.