通过 XML 文件创建自定义设计器作为 VSIX 2010 包
我们有一组 VS 2008 包，它利用自定义项目/项模板、围绕 XML 文件的设计器，用于使用 VS 进行内部产品开发。我们计划迁移到 VS 2010，并寻求将 VS 2008 包迁移到 2010。我看到已经使用 WPF/MEF 从头开始重写了 VS，但仍然不知道如何利用它来实现我们的目标。包。我看到了一些关于如何扩展基于 VS 2010 WPF 的文本编辑器的指南、示例和社区材料，但找不到任何关于如何使用 WPF/MEF API 在 XML 上实现自定义设计器的参考实现VS SDK。
到目前为止，我遇到的关于任何自定义设计器实现的唯一示例是Example.XmlWpfDesigner - http://code.msdn.microsoft.com/Designer-View-Over-XML-20a81f17 它没有谈论任何有关 WPF/MEF 自定义设计器的方式。
有人遇到过类似的参考实现吗？任何有关此事的帮助将不胜感激。
谢谢， 湿婆
We have a set of VS 2008 packages which leverages custom Project/Item templates, designers around XML files for our in house product development using VS. We are planning to move to VS 2010 and looking for migrating our VS 2008 packages to 2010. I see that there has been a rewrite of VS from ground up using WPF/MEF, but still could not figure out how we can leverage it for our packages. I am seeing some guidelines, samples and community material on how we should be extending the VS 2010 WPF based text editor, but could not find any reference implementations on how one should implement a custom designer on top of XML using the WPF/MEF APIs of VS SDK.
Only sample I have come across regards to any custom designer implementation so far was Example.XmlWpfDesigner - http://code.msdn.microsoft.com/Designer-View-Over-XML-20a81f17 which does not talk anything about WPF/MEF way of doing custom designers.
Has anybody come across any reference implementations along these lines? Any help regarding this would be much appreciated.
Thanks,
Siva
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您链接到的示例是设计人员通过 XML 文件查看的正确示例。它是一个用于编辑 VSTemplate XML 文件的 WPF 设计界面。
VS API 中唯一在 VS 2010 中迁移到 MEF 的部分是核心文本编辑器。虽然欢迎您使用 MEF 来实现设计器的实现细节，但您仍然需要与 VS COM API 进行交互以执行缓冲区管理、与源代码控制接口连接等操作...
The sample you linked to is the right one to be looking at for a designer over an XML file. It is a WPF-design surface that edits VSTemplate XML files.
The only part of the VS API's that moved to MEF in VS 2010 was the core text editor. While you are welcome to use MEF for the implementation details of your designer, you'll still need to talk to the VS COM API's to do things like buffer management, interfacing with Source Control interfaces, etc...