Blazor Standalone WebAssembly with ASP.NET Core Identity #231
Conversation
|
@JeremyLikness ... This is the wrong spot for Blazor samples. They go in ..... |
|
SPA and all of the other Identity samps should go in the main doc set sample repo here. The reason we have the split is just to apportion the management of the samps. I don't watch the main doc set samples repo, but I do keep tabs on the Blazor samples repo. Also, you'll notice that I use a different versioning scheme to make sure that all samples are updated every release. That's not done with the main doc set samps. |
|
Thanks for the clarifications. I'll move the Blazor one and switch to the other for SPA samples. I'm going to do Blazor Standalone WebAssembly, Blazor server rendered, Blazor wasm rendered, and blazor with external login. Should these all just be project folders under blazor-samples or do you want any sub-categories/directories in between? |
|
They go by versions, so you can place them into the |
|
... and if all goes well, you won't need to sweat them much after that. Each release, I'll update them. If I hit a problem, I'll give u a shout. You might only need to work on them again for some new security features that land in future releases if I can't understand what the updates should be. Thus far with the EFCore sample, I've been able to update it each release without trouble, including for BWA. Note tho that it's still RC1 ... I'll get to it in a bit to take it to RC2, or I'll just jump in near release and make it final release 8.0. I'm still slammed at the moment with other work, so I'm not sure when I'll reach it. I'll get to it tho ...... eventually! 🗻⛏️😅 |
|
Closing to move sample. |
Fixes #230