I am using nsis v2.51 with the once "modern" interface MUI.nsh and a few other plugins (FileFunc, StrFunc, x64 and some functions I wrote). I also have some super-plain installers with the ancient plain interface
lately I was plagued with AV false positives and I am considering updating to version 3.01. Will my existing v2.51 scripts work generating the same installer?
version 3 backward compatibility
5 posts
For the most part, NSIS 3 can compile any NSIS 2 script. The main difference is that NSIS 3 has unicode support.
FYI, FileFunc, StrFunc and x64 are code headers, not plugins.
FYI, FileFunc, StrFunc and x64 are code headers, not plugins.
Upgrading is not going to help with the AV false positives, it is better to just report them to the AV vendor...
thing is that MY executables inside the installer come clean, so the problem with the signatures must be coming from the NSIS components I use (system.dll etc), which will change with a new NSIS version. Of course that doesn't mean the new NSIS files will be considered clean either!
PS of course I don't mean that the NSIS components are viruses, but they could appear in installers that are considered viruses/Trojans, and thus are used as marks of dodgyness