This sample is so complicated and at the same time does not support the use case for 99% of people

Back when I was starting to implement SCIM for the company I am working for, I started with this sample and I didn't understand why it is so hard to implement a sample that is usefull to most people and there is no complications that is not required.

The FileProvider project contains 19 files which most of them has no added value for the developer who's goal is to start using Microsoft's SCIM library. Out of 19, 12 of them can be easily omitted just by using string files instead of Access Database and saving rows in it as JSON. Honestly, no one cares about CommaDelimitedFileAdapter, ColumnsFactoryy, IROW, ITabularFileAdaptor and etc.

Then there are parts that matters for the audiance.
- The solution is running on console app, while every developer wants to use it as a web API
- Thre is no implementation of Discovery API's like Schemas, ResourceTypes and ServiceProviderConfig