Visual Studio 2010 是否向后兼容 Visual Studio 2008 的插件？
我不想失去 Visual Studio 2008 中一些非常棒的插件，但我听说 Visual Studio 2010 将使用 MEF。 这是否意味着我可以告别我的跳舞香蕉？
I have some really great addins in Visual Studio 2008 that I don't want to lose, but I've heard that Visual Studio 2010 will use MEF. Does it mean that I can say goodbye to my dancing banana ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
Visual Studio 中有三个级别的可扩展性：
我可以确认 VS2008 插件在 VS2010 beta2 中工作得很好。 您只需编辑 .AddIn 文件并将“9.0”替换为“10.0”。
不过我不知道 VS 包。
There are three levels of extensibility in Visual Studio :
I can confirm that VS2008 Add-ins work perfectly well in VS2010 beta2. You just have to edit the .AddIn file and replace "9.0" by "10.0".
I don't know about VS Packages though.
除非方向与去年发布的第一个CTP相比有所改变，否则旧的插入方法仍然有效。 我们应该很快就会有一个新的测试版（我不确定很快是什么时候，但距离上一次测试已经过去五个月了）。
MEF 和使用 WPF 作为前端并不意味着旧的插入工具的方式将不再起作用。
Unless the direction has changed from the first CTP released last year, the old method of plugging in still works. We should have a new beta soon (I am not sure when soon is, but it has been five months since the last one).
MEF and using WPF as the front end does not mean the old way of plugging in tools will no longer work.
我不认为对此有任何最终说法，但基于 VS2010 似乎是一次重大重写（所有代码编辑器的东西都是基于 WPF）的事实，以及 MEF 被引入作为其可扩展性模型的事实，并且根据早期 VS 升级的经验，我非常怀疑你的所有插件是否都能继续工作......有些可能 - 但恐怕很多插件都需要升级。
马克
I don't think any final word has been said on this, but based on the fact that VS2010 seems to be a major rewrite (all the code editor stuff is WPF-based), the fact that MEF is being introduced as its extensibility model, and based on experience with earlier VS upgrades, I would highly doubt that all your plugins will just keep working..... some might - but a lot of them will require an upgrade, I'm afraid.
Marc
他们并没有在 VS 中重写所有内容。 仅 UI（已移至 WPF）。
当前的插件可以加载，但它们必须知道新的注册表项。 我们现在正在针对我们的数据库引擎进行测试。 有一些新的界面和方法可以进入 Visual Studio Extensions 的小 UI（想想 iPhone 商店类型概念）。 但现在（2009 年 6 月）不需要它们。
当然，这可能会改变，但我认为确保尽可能多的旧插件加载和运行符合微软的最佳利益。
They didn't rewrite everything in VS. Only the UI (moved to WPF).
Current plugins CAN load, but they have to know about the new registry keys. We are testing this right now for our database engine. There are some new interfaces and ways to get into the little UI for Visual Studio Extensions (think iPhone store type concept). But they are not required right now (Jun 2009).
That could change of course, but I think it is in MS's best interest to make sure as many older plugins as possible load and run.