-
Notifications
You must be signed in to change notification settings - Fork 162
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
Windows Services support #175
Comments
Related (but maybe outdated): https://techcommunity.microsoft.com/t5/MSIX-Deployment/Support-for-Windows-services/td-p/196484 |
Are there any news on this? |
Support for services in an MSIX is coming as part of the 20H1 release. It is in current insider builds. The functionality is not in MSIX Core at this time. Its an item in our backlog. |
@jvintzel do you have some news about the msix core support of windows service ? I actually try to install a .net core 3 app as service with msix install to have automatic update. i run the install over a powershell script so i have the hand about a lot of stuff but even with this im unable to run a SC create for example because i have no idea where the app is installed on my powershell script. thanks for your help ! |
No update. Right now we are completing some other work from items like MSIX app attach |
Any updates if this is something being worked on? Our company also have usecases for this at the moment. |
Adding a service is now officially supported for recent Desktop versions. However, no support for What if one wants to leverage benefits of @jvintzel Any guides/workarounds available? |
Many desktop apps install one or more windows services in addition to the main app, e.g. a licensing service, device communication service etc. Such apps ask for packaged installation even more than others since they do wider modifications to the system, which would be nice to easily "rollback" (uninstall). Is any work being done to support this?
P.S. Sorry for the bug label, I don't know how to ask a question/request a feature without creating a bug.
The text was updated successfully, but these errors were encountered: