-
Notifications
You must be signed in to change notification settings - Fork 757
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
fix: Pack add-ins discovery targets with the dev-server #19464
Conversation
… run them no matter the SDK sued by the project
@Mergifyio backport release/stable/5.6 |
🟠 Waiting for conditions to match
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19464/index.html |
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19464/index.html |
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19464/index.html |
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19464/index.html |
The build 154377 found UI Test snapshots differences: Details
|
@Mergifyio backport release/stable/5.6 |
✅ Backports have been created
|
…5.6/pr-19464 fix: Pack add-ins discovery targets with the dev-server (backport #19464)
linked to unoplatform/studio#43 (comment)
Bugfix
Pack add-ins discovery targets with the dev-server to be able to run them no matter the SDK sued by the project
What is the current behavior?
If a project uses the
Microsoft.NET.Sdk
the add-ins discovery might fail.What is the new behavior?
Targets are dynamically injected, no matter the SDK
PR Checklist
Screenshots Compare Test Run
results.