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

.vsconfig does not recognize Uno Extension in VS #962

Open
MartinZikmund opened this issue Sep 18, 2024 · 5 comments
Open

.vsconfig does not recognize Uno Extension in VS #962

MartinZikmund opened this issue Sep 18, 2024 · 5 comments
Assignees

Comments

@MartinZikmund
Copy link
Member

"https://marketplace.visualstudio.com/items?itemName=unoplatform.uno-platform-addin-2022"

@MartinZikmund MartinZikmund self-assigned this Sep 18, 2024
@jeromelaban
Copy link
Member

@MartinZikmund what does it do?

@MartinZikmund
Copy link
Member Author

This should (if it worked) suggest the user to install the Uno Platform extension, unless it is already installed - which is useful if a user opens an external Uno Platform app repository. However, it seems that in the current state it just pops notification about dependency missing, and hitting the Install button then opens an infinite loading VS dialog. Maybe it was a problem on my side though, as I might have installed a dev version of the extension instead of the prod one - need to verify and test it

@MartinZikmund
Copy link
Member Author

MartinZikmund commented Jan 6, 2025

Created https://developercommunity.visualstudio.com/t/vsconfig-extension-always-displayed-as/10823565 to figure out what is going wrong, until then removing the extension from .vsconfig - #1158

@jeromelaban
Copy link
Member

This specific behavior is happening when the installed build is not coming from the marketplace. Is your build a dev one?

@MartinZikmund
Copy link
Member Author

MartinZikmund commented Jan 7, 2025

@jeromelaban actually not, I made sure to uninstall and install the latest marketplace version and it still happens (in different versions of VS/different machines) - it really seems like a VS bug

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

No branches or pull requests

2 participants