netsurf, thanks for your response.
I guess that the code signing is meaningless to AV software based on two responses, one with and one without codesigning still flags the AV software. .
Charco, to compile without the runtime module, go to the ***Application Output ***of your project and then select the Runtime Module. Select the option, Do not merge the runtime module: I’ll distribute it separately and then compile your EXE and see if it still gets flagged by your AV software.
In my tests, with and without the runtime module, Symantec only flagged the one with the runtime module embedded.
If there is no other way around this and I have not completely tested this myself as yet but I have built other installations without the need of a runtime.
Use an installation program so both the runtime and your EXE are in the same installation package and put in the same directory, using the information below, you can run the runtime installation separately and silently without the user knowing.
After it is run, if possible, test that the runtime is installed, by a return code or by checking that the runtime exists. On Windows, XP, it is here, C:\Program Files\Common Files\HTML Executable Viewer{A528D704-C323-4636-A1F2-E9E8A725CDA9\HEIERun.dll, for the IE version, and then the runtime installer can be deleted. It is still in your installation package.
My installation will include shortcuts for the current user’s desktop and a menu item which will start the EXE in full screen mode.
My original plan was above with the runtime embedded so I can have the menu’s updated and the shortcuts created but by installing the runtime separately just adds a couple of more steps.
Post if you have any questions, on the above.
HawkeyeTX