-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Fix templates with Windows auth option #37607
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
Conversation
|
I manually verified Razore Pages CS ( |
|
@sebastienros I got that error in the past, I think you just need to uninstall all older 6.0 sdks, as I think that was how I got rid of that error |
src/ProjectTemplates/Web.ProjectTemplates/BlazorServerWeb-CSharp.csproj.in
Outdated
Show resolved
Hide resolved
pranavkm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The package version looks suspect
src/ProjectTemplates/Web.ProjectTemplates/content/BlazorServerWeb-CSharp/Program.cs
Outdated
Show resolved
Hide resolved
|
@Tratcher I checked the other templates. It looks like the argument was copy pasted in launchSettings.json files but this is not intended to work in the projects, unless for webapi c# which seems to be missing the windows auth code too. If you take a look at EmptyWeb templates for instance their csproj is very empty, so is the Program.cs file. Do we want to add Windows auth at that point? I think it's out of the scope of the current issue we are fixing. |
|
I assume we'd want to fix any template that had an -auth Windows command like WebApi, razor, mvc, blazorserver, etc. Follow up with @blowdart. |
|
That's a fair assumption |
|
/backport to release/6.0 |
|
Started backporting to release/6.0: https://github.com/dotnet/aspnetcore/actions/runs/1356998325 |
Fixes #37556