Create and automate professional MSI and MSIX packages for your desktop application.
Master Packager Dev - focus on your app, not the installer.
Who are you?
How It Works?
- Install Master Packager Dev software.
- Have all your app binaries (files, registries, services, etc.).
- Create a JSON project file that describing your installer using documentation.
- Run the command line:
mpdev build path-to-JSON-file. - Get MSI and MSIX installer packages, ready to distribute to your end-users.
Let Your Users Install Your App Today.
Master Packager Dev outputs high-quality MSI and MSIX installer packages.
These packages are ideal for:
1. Manual distribution: Store it in your preferred location so end users can download and install by simply double-clicking the installer.
2. Microsoft Store: Submit it to the Microsoft Store and distribute to your users from there. Both MSI and MSIX formats are Microsoft Store ready.
3. Enterprise deployment: Let enterprise customers deploy it using mass deployment solutions like Microsoft Intune or Configuration Manager.
Build an Excellent Installer for Your App Today.
Building a great installer can take months, yet most developers still fail.
When they fail, it becomes expensive for both developers and end users.
- Independent software vendors spend way too much time to learn all the technical details behind MSI and MSIX.
- Open-source maintainers lose community help because of a complex installer.
- Organizations spend money to re-package installers so they can work with enterprise deployment systems.
- Home users end up dealing with errors, stuck on old versions, or with software that never fully uninstalls.
Master Packager Dev built to save and your users money and time.
Auto-Update module
A professional, beautiful, and secure auto-update module that can be easily added to your MSI package.
The auto-update module checks the latest available version of your application, notifies the user, and installs updates silently.
When enabled, it can operate in enterprise environments and install updates in Program Files for users without admin rights - similar to how Google Chrome handles updates.
Upgrade experience
Great installer can check if previous version of the application is running and notifies user to save their work before continuing with upgrade. Most developers create this functionality from scratch on their own.
But you don’t need to spend time building something that should work by default - because it already does when building installer packages using Master Packager Dev.
Dependency management
Handle your app dependencies within your installer.
Set the installer to check for required dependencies and notify the end user if any are missing. For example, if you have a Word add-in, check whether Microsoft Office is installed.
Set the installer to check for and install missing dependencies using WinGet.
Moving Away from the WiX Toolset
We used to create MSI packages for our apps with the WiX Toolset.
- It was too complex to get started.
- Maintaining the project was a pain.
- No auto-update module or other advanced systems available out of the box.
- Paid support was too expensive.
- No real guidance, which leads developers to build poor-quality installers.
↓
World needed a solution that is simple, professional and affordable - Master Packager Dev.
Save your time. Skip learning things you'll only need once.
Installer creation is a time-consuming process that, to done correctly, can take months or even years to learn. Having analyzed over 10,000 installers from thousands of vendors—seeing both the good and the bad let us automatically answer and solve all common questions when building an installer with Master Packager Dev.
Don’t worry about these questions—we’ve got you.
- What are the best practices for installer creation?
- What are the limitations of MSI and MSIX package types?
- What are enterprises requirements for the mass distribution?
- How to automatically create new installer?
- How to create upgrade for previous versions?
- How to do automatic updates?
- Where to get help if I need one?
Frequently Asked Questions
- Will you be locked in?No, quite the opposite. If you decide to stop building installers with Master Packager Dev, you can stop renewing your subscription and switch to any other solution. Transitioning from Master Packager Dev to another tool will be significantly easier than starting from scratch with others, as you’ll already have all the necessary components and logic in place—just need to recreate them in the new solution. Plus, you’ll have a clear understanding of what the result should look like. Your existing created installers with Master Packager Dev will keep working forever.
- How can I convert my existing other solution project to Master Packager Dev?You can't and you shouldn't. We are fairly confident that your existing project in your current solution is complicated and probably do things developers shouldn't do when creating high-quality installer packages. Just know what files, registries, shortcuts, and other app components you need to install and where and we build out the Master Packager Dev JSON project file from scratch. It's fast. AI chats can help you read our docs and build out the project file. We can help as well. We love building installers. Just ask.
Azure Key Vault Explorer is built with Master Packager Dev
“ Master Packager Dev is something that has honestly made it possible for my app to be in the Microsoft Store. Before it, I struggled with makeappx.exe, but now I just run a command, and it’s done. ”
Arthur Thomas IV - Software developer of Azure Key Vault Explorer
