feat: AvaloniaVS defered loading #10523
Merged
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
Allow loading the AvaloniaVS extension when referencing the Avalonia nuget package Part of AvaloniaUI/AvaloniaVS#311
workgroupengineering
force-pushed
the
features/VS_Extensibility/Defered_Loading
branch
from
3c53e6d to
c41193b
Compare
maxkatz6
approved these changes
Mar 1, 2023
workgroupengineering
deleted the
features/VS_Extensibility/Defered_Loading
branch
|
You can test this PR using the following package version. |
maxkatz6
added a commit
that referenced
this pull request
Apr 19, 2023
…sibility/Defered_Loading feat: AvaloniaVS defered loading
maxkatz6
added
the
backport-candidate-0.10.x
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.
Allow loading the AvaloniaVS extension when referencing the Avalonia nuget package
Part of AvaloniaUI/AvaloniaVS#311
What does the pull request do?
What is the current behavior?
What is the updated/expected behavior with this PR?
How was the solution implemented (if it's not obvious)?
Doc
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues