These examples are old and out of date

[azure-ad-b2c]

These examples are old and out of date

[JasSuri]

The primary objective of this repo is to provide sample policies. We will consider updating, or removing all API samples and replacing with the interface/logical requirement instead.

Is there an issue being faced running a .Net Core 2.2 sample to demonstrate the end to end functionality?

Are you referring to the “related notes” to the policy files or the .Net API samples?

[mwwhited]

So many of your APIs have moved around to different assemblies or just generally jacked up by things like the trying to kill off JSON.Net kick your guys are on that want attempt to understand and update these examples on our own is a pain in the rear.

You are deprecating your own products and projects all the while not showing people have to use the current stuff with the new recommendations.

[JasSuri]

All of these samples work with any programming language you like. As long as your API can handle JSON it will work. Only for completeness we modeled them as an example alongisde the policies for demonstration purposes. All of the .Net Core 2.2 APIs do compile, if not, feel free to open this issue back up with a specific example for us to look into.

[mwwhited]

If you only intent is to show how the json works then you should clearly document the json payloads. As is your examples lead to issue when moving to other platforms and starting from scratch.

Again, if you are going to maintain these examples then don’t litter them all over the documented example on how to start your integration. And when you move dependencies make sure to clearly document those changes as poking around nuget for hours is not the best use of any developers time.

I know you clearly punted on documentation and useful example by hoping the open source/wiki world would do the work for you but hiding important details in deprecated code and hidden tabs in documentation does not make for a good development experience.

Heck, at the very least start removing the stuff that is no longer correct let alone useful such as everything that isn’t marked “preview” in the b2c docs.

[JasSuri]

We will document the JSON payloads and API interfaces into existing samples, and moving forwards with any new samples - appreciate this point. We will leave the old API samples in tact, since it still proves useful to just get up and running.