MAKEMSI quickly and reliably creates MSI files in a non-programmatic way\IntroductionQuick Start Guide (install, build small msi etc)Start your Own MSI

---

Before you start building your first msi...

If you are here then I will assume you have already installed MAKEMSI then built at least one of the installed sample projects and at least had a quick look at the project's source code (all as described in the previous "quick start" sections).

If you haven't done this to familiarize yourself with the basic processes then please don't complain about not understanding it when it fails to work...

Start your Own MSI

Now that you know that the basic environment is OK and you understand the build process we will take these successfully built files and make small incremental changes to the sample to resolve any remaining confusion or issues. I suggest making a backup of each successful change you make.

So I suggest:

1. Do not make any changes to any files in the MAKEMSI install directory tree. These files may/will be deleted on uninstall!

2. Copy all of these files to a new folder you created under your profile:
   • TryMe.mm
   • TryMe.ver
   • TryMe.rtf

   Note that this sample (like most) uses the "simplest framework for MSI creation" and this is what most people use, even if you don't intend to do this please continue with this section as the commands are identical.

3. Build it now (as a "sanity check") to prove everything is still OK and that you really do have all the files.

4. Rename the files at this stage to something more appropraite for your purpose, we will need to first make some minor changes to remove any references to the old names, the easiest way is to:
   1. Remove the line "#define VER_FILENAME.VER TryMe.Ver" from "TryMe.mm".
   2. Remove the line "; Licence = TryMe.rtf" from "TryMe.ver"

   As long as the base filename of the other files matches that of the ".mm" file then they will be picked up.

   If you didn't want a licence displayed you could now delete the ".rtf" file as the reference to it has been removed.

5. Build the ".mm" again as another sanity check.

6. As all your products should have a unique upgrade code you should use the "GUID Generation" shortcut to create a new unique GUID and modify the "Guid.UpgradeCode" statement in the version file, while you're there change the "ProductName" as well.

7. You can now experiment with makemsi commands to specify the simplest parts of your msi, working towards more complex requirements as you gain confidence.

   Remember that there are many other more complex samples which you can "borrow" commands from!

Please email me any feedback, additional information or corrections. See this page online (look for updates) MAKEMSI© is (C)opyright Dennis Bareis 2003-2008 (All rights reserved). Saturday May 28 2022 at 3:11pm Visit MAKEMSI's Home Page