-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Make all public API in dotnet-watch.dll internal and sealed. #28260
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
....DotNet.Common.ItemTemplates/content/Nuget/.template.config/localize/templatestrings.cs.json
Show resolved
Hide resolved
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.
Please avoid changes in templates as this PR is not related to them.
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.
Looks good from templating perspective
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
dotnet-watch.dll has been intended to be used as a tool, not consumed as a library and expose any extensibility points via public APIs.
@javiercn PTAL |
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.
Looks correct from what I can tell.
Are these APIs used by VS in some way?
No, VS doesn't use dotnet-watch at all. |
dotnet-watch.dll has been intended to be used as a tool, not consumed as a library and expose any extensibility points via public APIs.