-
Notifications
You must be signed in to change notification settings - Fork 335
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
Common Startup Task Support #10
Comments
See also #46 for related issue |
Would this also need to include affordance for System Tray apps/icons - which are not available in 10X, and not currently available for UWP apps. The System Tray/Notification Area has some of the least consistent UI of all Windows applications. With other taskbar flyout UIs now using Xaml and presenting a consistent UI/UX - could Microsoft try to come up with a secure and flexible UI presentation surface/context Menus/icon handlers which have graceful fallback for 10X and those devices like Hololens and Xbox? |
@andreww-msft - does #111 cover all the bases for this issue? |
Yes, covered in #111 . |
Proposal: Common Startup Task Support
Summary
Packaged applications have a specific
StartupTask
type that lets them manage tasks that run when the user logs on. Provide a type that gives the same startup task functionality across all kinds of applications, ideally modelled after theStartupTask
type.Rationale
There are many different documented ways to create and configure startup tasks for Win32 unpackaged applications. Packaged apps (UWP, Desktop Bridge) use the common
StartupTask
type. This disparity makes it hard to transition from Win32 to UWP or back. Windows should have a single strongly-documented API surface that lets apps create tasks that launch them at startup.Scope
Important Notes
Use of this API will not require a Win32 app get packaged, but the app might need to carry an artifact declaring the startup tasks in a way similar to how packaged applications declare them.
Open Questions
Should a Win32 app running elevated be allowed to enable their startup task for all users, or only the current user?
Should the API enable the complicated "run elevated at startup" task described in MSDN?
The text was updated successfully, but these errors were encountered: