在加载托管Bootstrapper应用程序之前调用脚本
我是WXS的新手，我想在加载托管Boottrapper应用程序之前运行一个设置某些注册表的脚本。我没有找到任何相同的文章。我通过使用自定义操作来解决我的要求，但是我只有在product.wxs of product。包装而不是捆绑包。wxs.s.但是补充说，它在执行时为时已晚。我希望我的脚本是双击我的bootstrapper exe时的第一个脚本。有可能吗？请帮忙
<CustomAction Id="CreateFileCA" BinaryKey="hello.vbs" Execute="immediate" VBScriptCall='' Impersonate="no" Return="check"/>
<Binary Id="hello.vbs" SourceFile="D:\hello.vbs"/>
<InstallExecuteSequence>
<Custom Action='CreateFileCA' Before='LaunchConditions'>NOT Installed</Custom>
</InstallExecuteSequence>
I am new to wxs and I want to run a script which sets certain registries,right before my managed bootstrapper application is loaded. I haven't found any article which talks about the same.I thought by using custom actions it would solve my requirement,but i am able to see the output of this script only when it is added in the Product.wxs of the induvidual msi packages and not in the Bundle.wxs.But adding it is too late by the time it executes.I want my script to be the very first script on double clicking my bootstrapper exe. Is this possible?Please help
<CustomAction Id="CreateFileCA" BinaryKey="hello.vbs" Execute="immediate" VBScriptCall='' Impersonate="no" Return="check"/>
<Binary Id="hello.vbs" SourceFile="D:\hello.vbs"/>
<InstallExecuteSequence>
<Custom Action='CreateFileCA' Before='LaunchConditions'>NOT Installed</Custom>
</InstallExecuteSequence>
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
自定义只能在MSI中使用。 V3在捆绑包中使用时默默地忽略了它，但是V4会发出警告。在V3中，在BootstrapperApplication之前不可能运行任何内容。运行代码的唯一方法是通过BA。
在V4中，有一个新的bundlextension概念在BA之前加载，但不应以这种方式使用它。对用户计算机的修改只能在应用过程中通过包装进行。
CustomActioncan only be used in an MSI. v3 was silently ignoring it when it was used in a bundle, but v4 will give a warning.In v3, it's not possible to run anything before the BootstrapperApplication. The only way to run your code is through the BA.
In v4, there is a new concept of BundleExtension that gets loaded before the BA but it should not be used in this way. Modifications to the user's machine should only be done by packages during Apply.