Skip to content

Have the Stable extension disable itself if it notices the preview extension installed #3822

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

Closed
StevenBucher98 opened this issue Feb 10, 2022 · 6 comments
Labels
Area-Build & Release Issue-Enhancement A feature request (enhancement). Up for Grabs Will shepherd PRs.

Comments

@StevenBucher98
Copy link
Contributor

Summary of the new feature / enhancement

If a user has installed the preview extension, the stable version should disable itself as to avoid any conflicts and issues with having both extensions enabled.

Proposed technical implementation details (optional)

No response

@StevenBucher98 StevenBucher98 added feature_request Issue-Enhancement A feature request (enhancement). labels Feb 10, 2022
@StevenBucher98 StevenBucher98 transferred this issue from PowerShell/PSResourceGet Feb 10, 2022
@ghost ghost added the Needs: Triage Maintainer attention needed! label Feb 10, 2022
@StevenBucher98
Copy link
Contributor Author

Oops put in wrong repo

@csandfeld
Copy link

I have both extensions installed, and tend to go back and forth between the two. Would be sweet if enabling one, would automatically disable the other if present, and vice versa.

@JustinGrote
Copy link
Collaborator

This would ideally be solved by a unified marketplace entry with prerelease versions (#3716) but that's blocked on microsoft/vsmarketplace#50 right now.

@JustinGrote JustinGrote added Area-Build & Release Up for Grabs Will shepherd PRs. and removed Needs: Triage Maintainer attention needed! Needs-Triage labels Feb 15, 2022
@JustinGrote
Copy link
Collaborator

Just noting this probably would have proactively avoided #3835, so there is a value to doing this.

@andyleejordan
Copy link
Member

I'm actually just going to close this in favor of #3716.

@ghost
Copy link

ghost commented Mar 16, 2022

Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Build & Release Issue-Enhancement A feature request (enhancement). Up for Grabs Will shepherd PRs.
Projects
None yet
Development

No branches or pull requests

4 participants