Updating docs and quick start samples to ASP.NET Core 2.1 / 2.2 #2664
Comments
Our plans for the docs are:
The main reason the docs have become somewhat stale is that Microsoft up-ended the ASP.NET Identity templates and somewhat broke our quickstart for it. That's a lot of work to keep chasing their template changes. |
@brockallen , would you go for traditional MVC or RP in your templates (point 2)? |
Work has started on the new quickstarts. They will be done in a way that it doesn't matter too much anymore which version of ASP.NET is used (at least that's my dream). We don't plans to do RPs. |
@leastprivilege , this issue has the tag "help wanted". Feel free to tell me if you need an input for testing or whatever. |
You can go to our docs and choose the UpdatedQs branch. QuickStart 1-4 are updated. A review would be nice. Thanks |
I am on it and have some proposals, mainly on the pedagogy side. I also found out that the discovery endpoint display
which is more detailed than the image snapshot you show. Is that expected or should be mentioned. |
image is fixed |
any other feedback |
tracking in #2536 |
Yes, feedback is coming. Does the intro section here http://docs.identityserver.io/en/latest/ needs to be updated for 2.1? I assume it doesn't. |
Everything is here this will replace latest - once @brockallen is done |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
All the docs and quick start samples are for ASP.NET Core 2.0.
Given the number of docs and quick start samples, it's a fairly big task to update them all and so I was wondering what work was in progress / planned in this area and what would be the best way of planning the remaining work?
I suppose another consideration is that ASP.NET Core 2.2 is scheduled for release by the end of the year. So would it make sense to skip over version 2.1 and just update the docs and quick start samples to version 2.2?
Whilst some of the work will be simply changing the version from 2.0 to 2.1 / 2.2, other parts will require more work. A couple of things that I can think of are:
The text was updated successfully, but these errors were encountered: