Code signing to help with Windows virus false positives

[Thomas Mader via Digitalmars-d]

On Tuesday, 11 October 2016 at 01:37:55 UTC, Martin Nowak wrote:
> On Saturday, 20 August 2016 at 13:45:11 UTC, Basile B. wrote:
>> "to MSI using innosetup" ?
>>
>> There's a misunderstanding here. Inno setup doesn't compile to 
>> MS installer, it's a complete independant solution.
>
> Whatever makes more sense. From my very limited understanding 
> .msi installers are natively understood installers in Windows, 
> and the weapon of choice for robust and more professional 
> installers.
> If innosetup is just another NSIS like tool, it might not solve 
> all our problems.
>
> We're fairly clueless here and could really use help here.
>
> Just signing the NSIS installers could work for now, any 
> support for this hypothesis.
> I tried to submit the latest release as sample to Microsoft but 
> their file upload had a size limit smaller than the binary.

I worked with NSIS and InnoSetup. InnoSetup is much cleaner and 
easier.
At work we switched from NSIS to InnoSetup and we create MSI 
packages from NSIS and InnoSetup packages IIRC.
I think it's better to go with InnoSetup because it might be more 
easy and probably more powerful than building MSI directly. But I 
don't have any experience with building an MSI installer and the 
feature set of MSI.
We are also signing the installer and all exe and DLLs inside.