I am an Apple user, and I want to give my App to someone running a Windows laptop. What do I need to do to prepare my App, and how do I install it on their laptop?
If you want to give it to a user or a few users then simply copy the built application folder to a usb drive & paste into their laptop(s). It doesn’t even need to be in the programs folder.
For more than a few you’ll want to look at innosetup & code sign your app.
Don’t forget to tick the windows build target in your project
If I’m reading you right, this is informal and personal. As such, there is no reason that you cannot just give them a zip of the Windows build folder. Just tell them to unzip it, open the folder and run the .exe. They should take care not to relocate any of the .dlls or subfolders. They do not have to “install” it per se.
For more widespread distribution, you will want to make an installer, using a tool like InnoSetup. It has a wizard that makes this easy—that is, till you move to the fun and expense of code-signing.
Wayne, I think you and I tied.
I would highly recommend to try and debug your app on Windows first.
if you have a Mac, get a trial copy of Parallels or VMWare (or similar) to install a trial of Windows on the Macbook as a virtual machine and try the app there yourself.
Otherwise you may get embarrassed when the app crashes for some reason on the first launch. e.g. because it can’t find a file it’s looking for.
Yes, I can second this suggestion. Use InnoSetup to make an installer. Then the user has just the one file to deal with, rather than the 30-odd that get added by the build. You will need to make an InnoSetup script (or config file) to tell Innosetup what files to include and what to call the installer. I do this in a VM under Win-11 and it doesn’t seem bothered about code-signing or suchlike.
If you’d like to build the Xojo Project and create the InnoSetup installer on any machine (e.g. on macOS - without switching to a VM for certain build tasks) - then have a look at this example which is using Docker (instead of a VM which you need to maintain):
GitHub: jo-tools/ats-codesign-innosetup
You can also omit the Post Build Script codesign
and just use the Post Build Script innosetup
to build a Window Installer without codesigning.
And remember (taken from wikipedia):
In June 2021, shortly before Microsoft’s announcement of Windows 11, Microsoft updated their lifecycle policy pages for Windows 10, revealing that support for their last release of Windows 10 will end on October 14, 2025.[60][61] On April 27, 2023, Microsoft announced that version 22H2 would be the last of Windows 10.