Closed josephdecock closed 1 year ago
The number of files changed is large, but mostly this is generated code. In most of the quickstarts, we just update the proj files. In the EF quickstart, we also regenerate migrations, and in the AspNet Identity quickstart, we re-run the template using 6.2's template.
Why is it necessary to update the quickstarts for a minor release?
Why is it necessary to update the quickstarts for a minor release?
We have a support case where someone is having difficulty with EF migrations during an upgrade. They aren't getting the server side session tables generated in their migration, and they noticed that our sample doesn't have that either. I updated and regenerated the migrations to verify our sample, and figured I might as well publish the results. Updating the other quickstarts was pretty trivial, and I was there anyway so I figured I might as well.
Updates quickstarts 1-5 to version 6.2