Skip to content

Added the Blazor survey link to the Blazor-Server project template #17434

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

Merged
merged 4 commits into from
Jan 16, 2020

Conversation

mkArtakMSFT
Copy link
Contributor

Description

We currently have the Blazor survey link in the Blazor WASM project, but don't have this link in the Blazor Server project template. This results in getting skewed data, which doesn't allow us to make reasonable decisions. We are now enabling this for Blazor Server projects too to cover all the Blazor users.

User Impact

The Index page in the Blazor Serer app will now have a link in the bottom (similar to what is there in the Blazor WASM project template) which will take users to the survey about Blazor.

Regression

No: this is something new which is going to be visible only in the new projects.

Risk

Minimal

Addresses #17433

@mkArtakMSFT mkArtakMSFT added the area-blazor Includes: Blazor, Razor Components label Nov 26, 2019
@mkArtakMSFT mkArtakMSFT added this to the 3.1.x milestone Nov 26, 2019
@mkArtakMSFT mkArtakMSFT added the Servicing-consider Shiproom approval is required for the issue label Nov 26, 2019
@mkArtakMSFT mkArtakMSFT reopened this Nov 27, 2019
@leecow leecow added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Dec 5, 2019
@leecow leecow modified the milestones: 3.1.x, 3.1.2 Dec 5, 2019
@vivmishra vivmishra modified the milestones: 3.1.2, 3.1.3 Jan 9, 2020
@vivmishra
Copy link

Moved to Mar as per Tactics. Will need to be explicitly approved for Feb, if required.

@mkArtakMSFT mkArtakMSFT modified the milestones: 3.1.3, 3.1.2 Jan 15, 2020
@mkArtakMSFT
Copy link
Contributor Author

Moving back to 3.1.2 per a later Tactics decision (@jamshedd , @vivmishra )

@dougbu
Copy link
Contributor

dougbu commented Jan 16, 2020

/azp run

@dougbu
Copy link
Contributor

dougbu commented Jan 16, 2020

/azp run aspnetcore-ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@dougbu
Copy link
Contributor

dougbu commented Jan 16, 2020

/azp run aspnetcore-ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mkArtakMSFT
Copy link
Contributor Author

The only failure here is unrelated and is tracked by https://github.com/aspnet/AspNetCore-Internal/issues/3467

@mkArtakMSFT
Copy link
Contributor Author

@dotnet/aspnet-build folks, the only failure here is unrelated and I've filed a separate issue to track that down. This PR is ready to be merged.

@wtgodbe wtgodbe merged commit 452a822 into release/3.1 Jan 16, 2020
@wtgodbe wtgodbe deleted the mkArtakMSFT/blazorLink branch January 16, 2020 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components Servicing-approved Shiproom has approved the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants