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

APPX packaged version for Windows Server 2016 #1413

Closed
nschonni opened this issue Jul 24, 2018 · 8 comments
Closed

APPX packaged version for Windows Server 2016 #1413

nschonni opened this issue Jul 24, 2018 · 8 comments

Comments

@nschonni
Copy link
Member

I was doing some reading for the docker-node Windows images and came across this https://blogs.technet.microsoft.com/nanoserver/2015/11/18/installing-windows-server-apps-on-nano-server/
Seems like the Nano Server won't support the MSI installation, but does have this new packaging.

Pros:

  • Better install for Windows Server 2016+
  • Maybe compat with Windows Store?

Cons:

@refack
Copy link
Contributor

refack commented Jul 24, 2018

I'm +1 on migrating (as semver-major). I don't have much love for the msi, as IMHO it's only value is for provisioning automation, so if WSA is the successor, I say we should move to it.

P.S. https://blogs.technet.microsoft.com/nanoserver/2016/04/27/packagemanagement-support-on-nano-server/

@joaocgreis
Copy link
Member

Our MSI does more than just copy files: it updates the PATH, installs ETW and PerfCtr, takes care of upgrades removing old files, and all of this in a very simple way. Thus, we can't move out of it without providing something with the same features that is as simple to use, the MSI is very useful for many of our users. For more advanced users we already have the Zip/7Z packages, but those can be confusing.

MSIX will be the successor to MSI, and we'll move to it as soon as it's ready to use and can provide us with the same features.

APPX would not be able to set the PATH or install ETW and PerfCtr, so I don't see much benefit over the Zip/7Z packages. @nschonni can you tell us about your use case, if/how APPX would be better than the packages?

@nschonni
Copy link
Member Author

I'm actually not suggesting dropping the MSI, this would be in additional format it. For the MSIX stuff, replacing MSI, that would probably be a different thread (and it's not really ready yet). I use the MSI for my own machines, and don't necessarily see that changing even with this format for my regular machines.

can you tell us about your use case, if/how APPX would be better than the packages?

  • GPG on Windows does have a great story. The MSIs are signed, and so are the APPX packages so you keep the package integrity checks
  • It seems to be Microsoft's recommended package format for the Windows server space

I'm not an expert in this, just reading through the docs and poking around on the official images.

@joaocgreis
Copy link
Member

The MSIs are signed, and so are the APPX packages so you keep the package integrity checks

That's a good point, verifying the Windows Zip/7Z packages is not so straightforward (well, it is if you have WSL available).

It seems to be Microsoft's recommended package format for the Windows server space

I believe MSIX will take over that as well.

Given the pros and cons, I don't see a pressing need for APPX now. I don't think we should produce official APPX builds as it's one more thing to maintain and MSIX is being developed. But if someone wants to go ahead and open a PR for APPX support, it would still be a good thing to have to enable anyone to build their own.

@refack
Copy link
Contributor

refack commented Jul 24, 2018

I was just thinking...
If we consider the front-end dev use case, where people need Node.js mostly to drive webpack or gulp or just npm, this actually might be a very interesting solution (APPX from the store for Windows 10)

@nschonni
Copy link
Member Author

Looks like since you're using Wix already, it might be fairly straight forward to add support https://www.firegiant.com/products/wix-expansion-pack/appx/

@github-actions
Copy link

github-actions bot commented Mar 8, 2020

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

@github-actions github-actions bot added the stale label Mar 8, 2020
@nschonni
Copy link
Member Author

nschonni commented Mar 8, 2020

Shoo stale bot

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

No branches or pull requests

3 participants