Home > Article > Web Front-end > Solution to the problem that node-webkit is packaged into an exe file and is falsely reported as a Trojan by 360_node.js
Recent projects require the use of node-webkit. Address the compatibility of legacy users and the 'data security' issues in their minds.
1. Download node-webkit
2. Create appName.nw file
3. copy /b nw.exe appName.nw TestAppName.exe
So far, the TestAppName.exe file has been generated in the directory, and it runs perfectly when double-clicked.
However, if I directly change TestAppName.exe to another directory, it cannot be opened.
Google Baidu’s solution: Use the Enigma Virtual Box tool and package it into an exe file. (Please refer to Baidu or Google for how to use Enigma Virtual Box)
Okay, it is indeed possible, but... the evil 360 anti-virus software actually reports a virus, and it is hopeless~
So continue to use Baidu Google...
Okay, enough nonsense, let’s talk about the method:
【3. copy /b nw.exe appName.nw TestAppName.exe】 After this step is completed, download a tool called Inno Setup Compiler.
Keep going to the next step (each step will have corresponding parameter and name settings) until the following picture:
The first red box is the file packaged with copy. The second red box is the dependency file that needs to be added (essential).
After filling it out, continue to the next step~ until the end.
Success! ! !
That’s all the content of this article, I hope you guys like it.