-
Notifications
You must be signed in to change notification settings - Fork 10.3k
3.0-Preview8 validation #12343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
area-blazor
Includes: Blazor, Razor Components
area-mvc
Includes: MVC, Actions and Controllers, Localization, CORS, most templates
Done
This issue has been fixed
task
Validation
This issue is used to track validation efforts
Milestone
Comments
I completed the validation for the SPA templates update for react and angular, so I'm done for preview8 validation. |
Finished my validation items. |
General validation issue that I found (doesn't fit under anything in particular): #12585 |
Finished my validation items. |
#12521 is done. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-blazor
Includes: Blazor, Razor Components
area-mvc
Includes: MVC, Actions and Controllers, Localization, CORS, most templates
Done
This issue has been fixed
task
Validation
This issue is used to track validation efforts
This issue will be used to collect all info related to the verification data for 3.0.0-Preview 8 release:
Build to use: daily build from https://github.com/dotnet/core-sdk#installers-and-binaries
If you plan to create any Azure resources specifically for the verification work, please create those in the 3.0-p8-validation resource group, in the ASP.NET Core Test subscription.
Make sure to create the issues in aspnet/AspNetCore repo and apply the proper area label and
Validation
label. Put the issue in3.0.0-preview8
milestone.The project to use to assign issues to:
After you create the issues, add them to the https://github.com/aspnet/AspNetCore/projects/4 project and unassign yourself from this issue.
The text was updated successfully, but these errors were encountered: