带有 .net 框架的 Microsoft 插件
我正在 .net 中使用 MAF 扩展应用程序框架。我已经实现了一个管道和所需的文件夹结构，当我在一个 dll 中实现加载项时，它工作正常。
如果我有一个复杂的加载项，其中一个 dll 实现合约，而一个支持 dll 执行内部逻辑。
当我构建此加载项项目时，主 dll 和支持 dll 会被复制到加载项文件夹中，此时框架无法从该文件夹中找到令牌。
I am extending an application using MAF in .net framework. I have implemented a pipeline and the required folder structure and it is working fine when I have the add-in implemented in one dll.
If I have a complex add-in where one dll implements the contract and a supporting dll performs the internal logic.
When I build this add-in project then the main dll and the supporting dlls are copied to the add-in folder and at that time the framework is not able to find the token from that folder.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您需要将支持程序集放入 GAC 中，因为管道域无法解析管道文件夹内的外部依赖项。 System.AddIn.Contract 中的某些接口似乎可能针对您所描述的场景（IServiceProvider 和 IProfferServiceContract），但 Microsoft 关于如何使用它们的示例为零。
微软在过去两年里对 MAF 完全保持沉默，真是令人遗憾。考虑到使用它的复杂性，缺乏复杂的现实世界示例是一个很大的障碍。沉默令人震耳欲聋……
You need to put the supporting assemblies into the GAC because the pipeline domains aren't able to resolve external dependencies from within the pipeline folders. Some of the interfaces in System.AddIn.Contract seem like they might be targeted for a scenario like you describe (IServiceProvider and IProfferServiceContract), but there are zero examples from Microsoft on how to use them.
It's a real shame that Microsoft has been so completely silent on MAF for the last two years. The lack of complex real-world examples is a big hindrance given the complexity of using it. The silence is deafening...