Creating just the exe or using an installer?

[VinnyAstro]

Hi.

I have a application fully developped on my computer, any changes on the application will be done from the same computer.

But this app is meant to be run on another computer, fully defined for it (I have a fresh new and empty computer and istall my app on it.)

Now I know that for the very first time I will create an installer, load it on the target computer and install my app with it.

But what about patches? Because I foresee there will be some (many) needed, so I test my app on the target computer, do some changes on my own computer, and then what?

• Is building a new .exe sufficient? I just replace it and all changed files in the destination?
• Should I build a new installer with the new .exe in it?
  • Will the installer uninstall my previous app on the targeted computer and install the new one by itself? Or should I do it first manually?
  • How would I create an uninstaller if thats not the case?
• In a more general way what is good practice for "patch version management" ?

I have never really used the builder before, so all this is a bit new to me.

Thanks for your help.

 - Vincent.

[UliB]

---

@VinnyAstro wrote:

• Is building a new .exe sufficient? I just replace it and all changed files in the destination?

This is possible, in some cases I do it that way, too. But it is a manual process, which you have to do. If you are the only one to support the other computer it might be ok, if another person will have to support the computer it might not be ok.

---

@VinnyAstro wrote:

• Should I build a new installer with the new .exe in it?
  • Will the installer uninstall my previous app on the targeted computer and install the new one by itself? Or should I do it first manually?
  • How would I create an uninstaller if thats not the case?

The installer will check if there is an older version of the software installed and will uninstall it before the new version is installed. It is important to use the Product Number and the Upgrade Code (both in the Version Information category of the installer properties). Upgrade Code is used to identify your software, if you change it the installer thinks it installs a different software. Product Number is used to determine which version is newer, so you should always increment it for a new version.

---

@VinnyAstro wrote:

• In a more general way what is good practice for "patch version management" ?

---

Using an installer to upgrade is a common process a lot of software creators use.

If you go the installer way you can hand out the installer to someone else, e.g. your IT department, and you are done. Right now you only have one computer. In the future is it possible to have more computers? I think the more computers you have the easier it is with an installer.

If you ever change the LabVIEW Development Version or a driver version, e.g. DAQmx, an installer can handle that accordingly.

UliB