ExternalAccess layering #73887
Merged
ExternalAccess layering #73887
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotnet-issue-labeler
bot
added
Area-IDE
untriaged
|
@dotnet/roslyn-ide ptal |
dibarbet
approved these changes
Jun 7, 2024
FWIW, it's possible that the correct layer for Razor might even shift after the Razor co-hosting work is complete. |
|
That's ok. Can move it again. |
This was referenced Jun 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move projects from
src\Tools\ExternalAccesstosrc\<layer>\ExternalAccessdirectory appropriate for each project.Allows us to apply directory-based configuration of each layer to these projects.
Does not move Razor and Xaml yet to lower likelihood of conflicts. These can be moved in separate PRs.