Forum Discussion
How to get started today
- May 08, 2018
Amit,
When looking to move your existing apps forward to MSIX, I'd recommend starting with the tooling vendor creating your packages today (if you have one). For example, if you're using the WiX Toolset to create your installation packages, we at FireGiant have created an extension to create .appx packages (and soon MSIX packages when Windows provides full support for MSIX) along with your .msi packages. I expect all the other major packaging vendors will support MSIX as well. If you don't have a vendor already, there are several to choose from (I think this presentation showed them: https://developer.microsoft.com/en-us/events/build/content/msix-inside-and-out-pptx).
As to your second question, MSIX will allow you deploy directly via SCCM. You can use the Windows Store for Business but it is not a requirement. MSIX deployment is much more like MSI in that way.
Hope that helps.
What if we have a mixture of Win7 & Win10 computers and WinForms & WPF apps. Can MSIX be used to replace ClickOnce and provide the deployment & auto-update for these scenarios? If so, how do we get started reviewing/testing to possibly convert? Thx
- jvintzelMay 09, 2018Bronze Contributor
Great feedback. We offer the SDK for folks that might want to minimize the packages they create. For Windows 7 it is essentially treating the MSIX file as a .cab file, minimizing the repackaging across multiple operating systems.
John Vintzel
Principal Program Manager Lead, MSIX
- vigneshwaran4264May 09, 2018Brass ContributorEagerly waiting for the tool to be released from MS.
- jvintzelMay 09, 2018Bronze Contributor
Stay tuned.. We will post some updates as more becomes available. Most likely sometime this summer.
John.