如何从 VB6 项目创建一个干净且可扩展的 NSIS 安装程序实现？
我正在使用 VB6 包装更新我的安装程序NSIS 安装程序的部署向导。
我的项目使用的文件列表多种多样，使用不同的路径和文件类型。例如，
[email protected],$(AppPath),,,8/30/10 10:23:54 AM,49152,1.0.0.1
....
[email protected],$(AppPath),,$(Shared),12/6/06 10:14:56 AM,12704,0.0.0.0
....
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/23/98 11:00:00 PM,103744,6.0.81.69
....
最初，我计划将每个文件硬编码到 NSIS 脚本中，但对于我团队中的新手来说，实际更新我的代码会很麻烦。很难重用和扩展。
然后，我计划为每个路径创建多个文件夹，以及文件应经历的过程类型。例如，一个 app_path_selfregistered 文件夹，我可以在其中放置新文件并重新编译我的安装程序。我觉得这不是真正可扩展且干净的解决方案。
最后，有人建议我创建一个我要调用的外部脚本，但我不确定如何实现它，也不知道比我的第一种方法有什么优势。
有什么想法如何干净地创建一个可扩展的 NSIS 安装程序，在其中我可以轻松更新到新文件及其更新版本？
谢谢
I am updating my installer from using the VB6 packaging & deployment Wizard to the NSIS installer.
The list of files my project uses are diverse, using different paths and types of files. For example,
[email protected],$(AppPath),,,8/30/10 10:23:54 AM,49152,1.0.0.1
....
[email protected],$(AppPath),,$(Shared),12/6/06 10:14:56 AM,12704,0.0.0.0
....
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/23/98 11:00:00 PM,103744,6.0.81.69
....
Initially, I was planning to hard code every single file into the NSIS script, but it would be cumbersome for a newbie in my team to actually update my code. It is hard to reuse and scale.
Then, I was planning to create several folders for each respective path, as well as the type of process that the file should go through. For example, an app_path_selfregistered folder in which I could drop the new files and just recompile my installer. I felt that it was not really scalable and clean solution.
Finally, someone suggested me to create an external script that I would call, but I am not sure how to implement it nor what would be the advantage over my first approach.
Any ideas how to cleanly create a scalable NSIS installer in which I can easily update to new files as well as newer versions of them?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论