Skip to content
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

Ensure existing usages of InterceptsLocationAttribute are onboarded to the new checksum-based approach #72855

Open
RikkiGibson opened this issue Apr 2, 2024 · 1 comment

Comments

@RikkiGibson
Copy link
Contributor

RikkiGibson commented Apr 2, 2024

Prerequisite: #72133

Once we ship the checksum-based interceptors pattern we will want to check in with all the partners who have onboarded to the .NET 8 experimental feature and work with them to get them moved to the new checksum-based approach.

Partner issues:
dotnet/runtime#101079
dotnet/aspnetcore#55152

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Compilers untriaged Issues and PRs which have not yet been triaged by a lead labels Apr 2, 2024
@jaredpar jaredpar added this to the .NET 9 milestone Apr 5, 2024
@jaredpar jaredpar added Bug New Feature - Interceptors and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Apr 5, 2024
@jaredpar jaredpar modified the milestones: .NET 9, 17.12 Apr 15, 2024
@RikkiGibson
Copy link
Contributor Author

RikkiGibson commented May 9, 2024

Before we remove the path-line-column support, let's report a warning when that attribute signature is used, e.g. late in the .NET 9 cycle. then post-NET 9 we can fully remove.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants