FPA
FPA copied to clipboard
FreeCAD
Publish FreeCAD on the Microsoft store
Need to check:
- [x] What is the process to follow (https://github.com/FreeCAD/FPA/issues/5#issuecomment-1511663700)
- [ ] What are the technical requirements, ie. what do we need to change to our packaging process
- [ ] Are there any fees? If yes, are there exceptions for open-source projects?
IIRC, Tantacrul recently posted a tweet about the Microsoft store (it was about removing imposter MuseScore apps that were masquerading as the official MuseScore project). Perhaps he could offer us some tips? CC @Tantacrul
I've just contacted a former colleague at Microsoft to see if there's someone who can reach out and take you through the process. There might be a free option for a FOSS product, so you don't have to pay the upfront registration fee (approx $100). If I get any info back, I'll get in touch to let you know.
It is infinitely easier to publish on the MS store than it used to be. Basically, if you have an .exe file and can do a silent install, you're there.
Question from Microsoft: Sure! Did they want to publish an unmodified win32 app, use an MSIX package with win32app or do a full UWP app?
CC @donovaly do you mind participating in this thread as well given your experience with Windows packaging for FreeCAD ? TIA
Question from Microsoft: Sure! Did they want to publish an unmodified win32 app, use an MSIX package with win32app or do a full UWP app?
Hi @Tantacrul, I am Uwe and responsible for the Windows installer of FreeCAD. If you could help me to bring FreeCAD to the Windows store, I will be happy. Our installer is built with NSIS. It is a .exe and 64bit only. Here is for example our latest release: https://github.com/FreeCAD/FreeCAD/releases/download/0.19.4/FreeCAD-0.19.4-WIN-x64-installer-2.exe
Perfect. I've sent that through and let's see what they say. Incidentally (I forgot about this), they very confusingly use the term 'win32 app' when talking about uploads to the store. We also just used a 64bit .exe but for some reason were classified as a 'win 32 app'. God knows why.
Anyway, when I get a response, I'll let you know. I'm hoping they'll offer you a contact to help you through the process.
@luzpaz do you want to follow up with this one? May I assign it to you?
@yorikvanhavre, Sure, but lets ask @donovaly first.?...since he can make changes directly to the Windows installer and there would be less liaising necessary.
Yes, in any case we all look into it. Thanks a bunch, @Tantacrul ! the windows store and its policies look like a maze...
Email sent + CC'd yorik
I did not get any mail. I sent @Tantacrul an email but since I don't know the email addresses of luzpaz nor Yorik, I could not CC you guys.
was there progress here?
Yes, but this requires up to months. We are on it.
Whole process at https://learn.microsoft.com/en-us/windows/apps/publish/publish-your-app/overview?pivots=store-installer-msi-exe
- [ ] 1. Create your app by reserving a name Reserving your app's name is the first step toward distributing it via the Microsoft Store.
- [ ] 2. Create an app submission for your app App submissions contain all of the information needed to distribute your app in the Microsoft Store.
- [ ] 3. Set your app's price and availability Specify how, when, and where your app will be available to customers, your app's pricing model, and whether you'll offer a free trial.
- [ ] 4. Specify your app's properties App properties describe important details about your app including requirements, capabilities, and your contact information.
- [ ] 5. Upload your app's packages Upload your app's installer to the Microsoft Store.
- [ ] 6. Create your app's store listing Create your app's page in the Microsoft Store.
- [ ] 7. Manage your app's submission Provide details about how you would like Microsoft to process your app submission.
- [ ] 8. Get your app certified Microsoft's app certification process helps ensure only the highest quality apps are published on Windows.
Maybe we can enable a github project for this since there are multiple steps to walk though? Each of them can be a ticket
Maybe, but there will likely be only one same person doing all these steps, so creating separate issues might be counter-productive...
I'm reading the docs already, and in the first one they say your name will be reserved for 3 months. So we'd better do it only when we are ready with the other steps. Iḿ still reading the rest to get an idea
uwe should take a look at step 5 since he's generating installer. https://learn.microsoft.com/en-us/windows/apps/publish/publish-your-app/upload-app-packages
CC @donovaly 👋👆
I created a Microsoft Partner ID for the FPA, but it's crazily complex and looks nothing like in the docs :sweat_smile:
We now have an EV certificate that we can use to sign the FreeCAD executable, but it might be that we got the wrong kind of EV cert... We need to test first and see what happens. But as far as I understand that's a different story than putting FreeCAD on the MS store.
I haven't looked more at it, I'll try to get back to it this month
@yorikvanhavre / @adrianinsaval any news on this? Would be great if 1.0 could be shipped in the MS store.
There is a lot of crap in the store from fake organizations, all paid.
I hope no one will pay for these if they want to try 1.0 when the news spread:
I believe we don't have a singing key yet. From what I had researched I think this is the option that makes the most sense for us: https://shop.certum.eu/open-source-code-signing.html
or alternatively this: https://shop.certum.eu/open-source-code-signing-on-simplysign.html
or alternatively this: https://shop.certum.eu/open-source-code-signing-on-simplysign.html
I would say this one may be more interesting for us, as it does not require a physical device?
If you package the app as MSIX, signing is not needed as it is automatically done by Microsoft when publishing to the Store and users would benefit from automatic updates. An MSIX package can be created from the classic installer (and has been done by many Win32 applications such as Inkscape, Blender, LibreOffice): https://learn.microsoft.com/en-us/windows/msix/packaging-tool/create-app-package
