User:Zinthose: Difference between revisions
From NSIS Wiki
Jump to navigationJump to search
No edit summary |
m (→About) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== About == | == About == | ||
My primary job function is to repackage software for deployment in my company using the Altiris Software Delivery system. I choose NSIS for the following reasons. | |||
# Unicode Support - My company is international and often the package requires the user prompting in several languages. | |||
# Small foot print - When deploying the packages thousands of systems to a remote sites, size matters. | |||
# Powerful scripting /custom actions - Allows for detailed system validation before the install proceeds. | |||
# Custom Return Codes - Altiris software deployment's reporting relies heavily on the return codes generated by the installs. | |||
# It's not MSI - Windows Installer packages are fine for installing software but was not designed for repackaging. | |||
# No scripting engines required - VBScript is fine for simple tasks but there is a greater chance that a VBScript will fail verses an executable. | |||
<pre style="color: red; font-size: 1.5em; font-weight: bold; | |||
white-space: pre-wrap; /* CSS 3 */ | |||
white-space: -moz-pre-wrap; /* Mozilla, since 1999 */ | |||
white-space: -pre-wrap; /* Opera 4-6 */ | |||
white-space: -o-pre-wrap; /* Opera 7 */ | |||
word-wrap: break-word;">[2016-01-07] | |||
I have returned to programming in NSIS and will be updating my contributions and adding new ones soon!</pre> | |||
== Code == | == Code == | ||
| Line 8: | Line 25: | ||
=== Headers === | === Headers === | ||
{| border="1" cellpadding="5" cellspacing="0" | {| border="1" cellpadding="5" cellspacing="0" | ||
| [[Stacks]] | | [[stacks.nsh | Stacks]] | ||
| Set of Macros for manipulating the stack | | Set of Macros for manipulating the stack | ||
|- | |- | ||
Latest revision as of 12:34, 7 January 2016
About
My primary job function is to repackage software for deployment in my company using the Altiris Software Delivery system. I choose NSIS for the following reasons.
- Unicode Support - My company is international and often the package requires the user prompting in several languages.
- Small foot print - When deploying the packages thousands of systems to a remote sites, size matters.
- Powerful scripting /custom actions - Allows for detailed system validation before the install proceeds.
- Custom Return Codes - Altiris software deployment's reporting relies heavily on the return codes generated by the installs.
- It's not MSI - Windows Installer packages are fine for installing software but was not designed for repackaging.
- No scripting engines required - VBScript is fine for simple tasks but there is a greater chance that a VBScript will fail verses an executable.
[2016-01-07] I have returned to programming in NSIS and will be updating my contributions and adding new ones soon!
Code
Functions
Headers
| Stacks | Set of Macros for manipulating the stack |
| Verbose Print Macro |
In Development
Plug-in DLL's
- Altiris Server integration.
- Progress: Concept
- Security Plug-in to prevent installation on systems that do not belong to an approved domain.
- Progress: Concept
Headers
- LGP Startup/Shutdown Script
- ALPHA Release
