ILMerge 和本地化资源程序集
我们有一个应用程序，其编译时的结构如下所示：
- Foo
- nb-NO
- Text.resources.dll
- sv-SE
- Text.resources.dll
- Bar.dll
- Foo.exe
- 文本.dll
- nb-NO
是否可以对此使用ILMerge？你会怎么做？
We have an application whose structure when compiled looks something like this:
- Foo
- nb-NO
- Text.resources.dll
- sv-SE
- Text.resources.dll
- Bar.dll
- Foo.exe
- Text.dll
- nb-NO
Is it possible to use ILMerge on this? How would you do that?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我问了这个问题的我自己的变体，并最终得到/实现了一个答案：
单程序集多语言 Windows 窗体部署（ILMerge 和卫星组件/本地化） - 可能吗？
希望这会有所帮助。
I asked my own variant of this question and eventually got/implemented an answer:
Single-assembly multi-language Windows Forms deployment (ILMerge and satellite assemblies / localization) - possible?
Hope this helps.
免责声明：我在生产 Dotfuscator 的公司工作。
可能还有其他我不知道的替代方案，但我很确定 ILMerge 不会这样做。
另一种方法是使用 Dotfuscator Pro，这是一种商业产品，我确信它可以正确地将程序集链接在一起，并且可以正确链接输入程序集集的任何卫星资源程序集。我们提供免费试用版，以便您对其进行测试并确保它适用于您的特定场景。
Disclaimer: I work for the company that makes Dotfuscator.
There may be other alternatives out there that I am not aware of but I am pretty sure ILMerge does not do this.
An alternative would be to use Dotfuscator Pro, a commercial product that I know for certain will correctly link together assemblies and does correctly link any satellite resource assemblies for the set of input assemblies. A free trial is available so that you can test it out and make sure it works in your specific scenario.
根据此处的评论之一，如果您愿意放弃智能感知，或者维护单独的并行 msbuild 文件，您可以将 DLL 设为“netmodules”。此 0f 课程假设您拥有 DLL 的源代码。
According to one of the comments here, if you're willing to give up intellisense, or perhaps maintain separate parallel msbuild files, you can make your DLLs "netmodules" This 0f course assumes you have the source code to your DLLs.