Skip to content

Conversation

guardrex
Copy link
Collaborator

@guardrex guardrex commented Aug 15, 2025

Fixes #35936

I should hear back from all before merging, as there's an editorial decision to be made on this one.

Changes

This is only for empty (web) and BWA (blazor) template-based app creation per Damian's remarks ...

The project templates for ASP.NET Core Empty (web) and Blazor Web App (blazor) have been updated with a new option ...

Tooling guidance generally isn't versioned

We usually don't version VS tooling guidance. We assume that the dev is using the latest tooling and the latest project templates for our tutorials. This updates our guidance to include coverage for the new "Use the .dev.localhost TLD in the application URL" option. I made the update across the repo, using whatever styling the doc author had in place without versioning.

However, this is a project template-based setting. Therefore, it's really only going to appear for >=10.0 project template-created apps. I lean in the direction of just going ahead with the updates unversioned as they appear on the PR. Most apps are created for late-model releases, right? ... with late-model VS, right? If we can avoid versioning for tooling instructions, it's best.


Internal previews

📄 File 🔗 Preview link
aspnetcore/blazor/tutorials/movie-database-app/part-1.md aspnetcore/blazor/tutorials/movie-database-app/part-1
aspnetcore/blazor/tutorials/signalr-blazor.md aspnetcore/blazor/tutorials/signalr-blazor

This comment was marked as resolved.

@guardrex guardrex self-assigned this Aug 15, 2025

This comment was marked as resolved.

@guardrex guardrex requested a review from danroth27 August 15, 2025 15:14
Copy link
Contributor

@tdykstra tdykstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One comment for you to look at.

This comment was marked as resolved.

This comment was marked as resolved.

@guardrex
Copy link
Collaborator Author

@tdykstra ... It's done. This is just for the Blazor tutorials then, which don't have screenshots of VS for that bit.

WRT the versioning aspects, I'll wait to hear from @danroth27 and @wadepickett before proceeding.

@guardrex
Copy link
Collaborator Author

BTW @tdykstra @wadepickett ... I already messaged Cassie about this but received no response. Would you consider seeing if they'll 🛑 the constant PoliCheck Scan Report comments when the scan passes? It's generating a lot of unnecessary comment churn and email pings.

@wadepickett
Copy link
Contributor

BTW @tdykstra @wadepickett ... I already messaged Cassie about this but received no response. Would you consider seeing if they'll 🛑 the constant PoliCheck Scan Report comments when the scan passes? It's generating a lot of unnecessary comment churn and email pings.

There was a discussion on this that was going on and still active this morning. I think as of this morning it may not have been resolved yet but stakeholders understand the problem and they may be close to changing it for the better.

Copy link
Contributor

@wadepickett wadepickett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@guardrex guardrex removed the request for review from danroth27 August 18, 2025 13:45
@guardrex
Copy link
Collaborator Author

Dan ... if you see this ... I don't need to bother you with this one after all, so I removed your review ping. I'm only going to call out the .dev.localhost TLD VS setting on the two Blazor tutorials.

@guardrex guardrex merged commit bf395e8 into main Aug 18, 2025
3 checks passed
@guardrex guardrex deleted the guardrex/blazor-add-vs-entry branch August 18, 2025 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[10.0] Blazor tutorial VS setup guidance: Add .dev.localhost TLD option
3 participants