Conclusion

As you could seen in the previous topics, there’s a lot of things you have to pay attention when creating a portable launcher. You have to ask as many “What if?” questions to yourself as you can and try to find the best possible solutions for them.

I’m sure that the script we made could be made more better and nicer but I think that will do now. For example, you may use if clauses to test if there’s a local install of the software on the host PC or if there’s a need to restore registry settings and so on.

In this chapter you’ve learned how to capture changes that were made during the install process, to what changes you should pay attention and how to find registration data. You’ve also learned how to build up the NSIS script, how to save and restore registry keys from and to .reg files, how to launch an application and how to delete files.

That’s the basics of creating a portable launcher. In the next chapter you’ll find how to create a launcher for a software which will do the following:

• saves and restores settings in the registry,
• creates directory, copies and deletes files,
• renames files to the logged in user’s name,
• registers and unregisters .dll or .ocx files,
• silently installs .msi files,
• etc.


Despite the list above you won’t learn so much new things in this chapter because you know almost everything you have to know to create your own portable launchers.