-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
What's on the Roadmap? #2864
Comments
Can you install apps using winget with Microsoft Store disabled? If Microsoft Store must be enabled to install apps using winget how can you prevent users installing other apps from the Microsoft Store interface? |
@mdonaghy325 I'm going to close this issue since it's essentially duplicating a discussion. Feel free to ask questions using GitHub Discussions. There is a subtle distinction between the store being disabled and the store client being disabled. If the store is in fact disabled, WinGet would not have the ability to install packages from the store. If only the UI is disabled, but the store service is still available, packages may be installed from the store. |
Thanks for reply
Would you be able to point me towards instructions on how to disable Store client UI and keep Store enabled
|
I'm not super familiar with all the options. A quick search turned this up: |
Discussed in #2063
Originally posted by denelon April 1, 2022
Many people have asked questions about the roadmap and how we prioritize the features we are working on. In the spirit of transparency, I'll share our philosophy.
We have a few competing priorities and limited resources. In general, we use Milestones to give a hint as to what we're working on, and when the milestone could be "code complete".
A numbered milestone represents the next features we're targeting in the next stable release. The V.Next milestone is a placeholder for some asks we're considering in a near milestone. Work items will be moved in and out as time and resources allow.
In some cases, we have strategic work taking priority. This happened with support for Apps in the Microsoft Store. Another area is the work to integrate with Intune. Others may come up in the future.
The next set of work items to be prioritized are based on "impact". These are items that would substantially improve capabilities. These items would be things like support for portable applications, dependencies, package pinning, and channels.
Last, but certainly not least are features and bugs with the most 👍 indicating community support.
The text was updated successfully, but these errors were encountered: