I noticed that every PortableApps applications seems to have at least 1 '.nsh' file in its folder.
I'm just curious:
1. What does "nsh" stand for?
2. What generates these files?
3. What is their purpose?
Thanks.
New: Kanri (Oct 9, '24), Platform 29.5.3 (Jun 27, '24)
1,100+ portable packages, 1.1 billion downloads
No Ads November!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I noticed some PortableApps application folders also have '.nsi' files. I am interested in learning the answers to the above 3 questions for them as well.
1. .nsi and .nsh are NSIS file endings. (See here)
2. Developers create these files
3. depends on the code within
Thank you for the tips.
Using them as a lead, I was able to find all the answers:
The default extension for a script file is .nsi. Header files have the .nsh extension. Header files can help you arrange your script by dividing it to more than one block of code, you can also put functions or macros in header files and include the header files in multiple installers. This makes updating easier and it also makes your scripts easier to read. To include a header file in your script use !include. Header files that reside in the Include directory under your NSIS directory can be included just by their name. For example:
!include Sections.nsh
A NSIS script contains Installer Attributes, Pages and Sections/Functions.
Source:
https://nsis.sourceforge.io/Docs/Chapter2.html