NSIS v3.01

[Anders]

NSIS 3.01 adds new icons, improves documentation, fixes translations, and includes the usual collection of bug fixes and improvements.

• Release Notes
• Known issues:
  • WinForms/GDI+ font failure in 3rd-party plug-ins on Win7 (NSIS 2.47-2.51 and 3.0b3+)
• AV false positives (Setup & Example1)
  • ALYac (Setup)
  • Baidu (Setup)
  • Bkav (Setup)
  • McAfee-GW-Edition (Setup)
  • Qihoo-360 (Example1)
  • Rising (Example1)
  • Symantec (Setup)
  • Sourceforge [Unknown engine, 20161211]

[Pawel]

@Anders,
This release is 3.01.
It means?
Major: 3 Minor: 0 Revision: 1 Build: 0

or

Major: 3 Minor: 1 Revision: 0 Build: 0

or

Major: 3 Minor: 01 Revision: 0 Build: 0

Maybe it is not bad idea to add version info to NSIS.exe and makensisw.exe. How do you think?

[rainwater]

Sourceforge is showing the installer as "Malware" and doesn't let you download it without warning you first.

[Crayon2000]

This project might benefit from using Semantic Versioning.

[Anders]

Originally Posted by Pawel

This release is 3.01.
It means?

How could you think it might be 3.0.1 when there is only one dot?

It is version 3.1.0.0 if you want to be specific.

3.01 and 3.1 is the same thing but we are using that scheme because people seem to be confused with 3.1 vs 3.10 and 3.9 vs 3.10.

Originally Posted by Crayon2000

This project might benefit from using Semantic Versioning.

We are not strictly Semantic Versioning compliant but pretty close but those semantics supposedly only applies to APIs and we are many things (product, language, plug-in host etc). The "product" and language are somewhat tied together while the plug-in API uses separate numbers even though it is also tied to features offered by the language/exehead. The plug-in API is still v1.0 and unchanged since 2.45.

On top of all this the compiler has its own host API used by MakeNsisW and 3rd-party IDEs. Before 3.1 there was no version numbers for it but it now loosely follows the main version number. There are probably less than 10 people on the planet that care about this though.

[Pawel]

Thank you for clarification. Now I know

[Koopa]

I appreciate the work for these new icons, but some critics though.

The MakeNSIS icon doesn't look related to NSIS at all, I always think, that I have some kind of Microsoft Visual Studio icon in my taskbar, why do you not add some 'NSIS' text to the icon like it was present in the old icons? It is really hard to accociate the new icon with NSIS.

Same for the installer icon, some NSIS text would be helpful.

This is no offense.

[Anders]

It is supposed to look like a N and at the same time, installing and uninstalling arrows IIRC.

[JasonFriday13]

I didn't know those were arrows, all I saw was a weirdly shaped N and a bunch of triangles. But now that you have pointed it out, all I see now is arrows .

I actually think it is a good thing, nearly half of the icons on my desktop are circle based, and circle based icons are so XP / Vista. It's about time the icon design got updated.

[Yathosho]

If anybody needs to incorporate the new logo, please use the files from the official repository

https://github.com/idleberg/nsis-logo-v3

[GTVic]

Is it possible to run 2.46 and 3.01 in parallel? Thanks

[Anders]

Originally Posted by GTVic

Is it possible to run 2.46 and 3.01 in parallel? Thanks

Yes, makensis does not care. Some registry settings are shared (recent file list in MakeNsisW etc) while the file type registration only works for the version you install last but there are no major issues.

I have multiple versions installed and use a shared directory for 3rd-party plug-ins: http://nsis.sourceforge.net/How_can_..._installations

[dothebart]

With the rise of https://chocolatey.org/ script controlled and unattended installation becomes more and more a reality also on windows.

Its advised to wrap NSIS installers into that using the /S switch. As it seems a good practice to use `DetailPrint` to output status; however, there doesn't seem to be a way to get all that usefull information output into a logfile or even the console? So if the installer fails in silent mode, its hard to tell where that happened?

Could it be a good addition for NSIS 3 to become able to CC that to a logfile?

[Anders]

I'm not very impressed with Chocolatey, not only are they currently one NSIS version behind but they have been behind now for 6 months! And to top it off, they get the version numbers wrong.

Anyway, install authors are free to use the DumpLog plug-in or the LogEx plug-in or any other solution if they want to output more details to a file. The logging version of NSIS could also be used.