Visual Studio 11抛弃宏（中英文版）

投递人 itwriter 发布于 2011-10-11 14:30 评论(0) 有1359人阅读  原文链接  [收藏]  « »

　　在 Visual Studio 11版本中，用户将无法使用宏。这标志着：近十年来，头一个 Visual Studio 的版本无法允许向 IDE 中随意嵌入宏扩展。不过，完整编译的扩展仍可以创建，新的项目模板也可以加入，这让整个过程变得更加方便。

　　根据 Microsoft 所做的使用率跟踪数据，Visual Studio 中宏的使用人数不到开发人员总数的1%。这还不足以让 Microsoft 放弃这个功能，Visual Studio 中的宏功能维护成本过高，是另外一个原因，与其他功能不同，对宏的支持，必须要随着 Visual Studio 每个新版本更新，并做大量令人疲倦的测试。理论上，用户应该可以在宏 IDE 中录制并播放任何功能，这给微软的维护增加了巨大负担。

　　Matt Kaufman 说：宏 IDE 已经好几个版本都没有更新了。用户把它启动之后，很快就能看出来它像一个老版本的 Visual Studio。更麻烦的是：它还是只支持 Visual Basic。用户不能使用 C# 或是其他新的 .NET 语言来创建宏。

　　如前所述，对扩展性的支持现在包括一些新的项目模板。下表中的模板支持 C# 和 VB：

• Visual Studio Package：供过去的 VSPackage 风格插件使用。
• Editor Classifier：供创建自己的语法高亮使用。
• Editor Text Adornment：用来在编辑器窗口内创建带颜色文本。
• Editor Viewport Adornment：用来放置与编辑器的视觉外观相关的视觉元素。
• [VB/C#]工作项模板
• [VB/C#]项目模板
• VSIX Project：这是新的插件模型，在 Visual Studio Gallery 里面最常见。
• Windows Forms Toolbox Control
• WPF Toolbox Control

　　除了语言特定的模板之外，还有一个常用的扩展文件夹，包括：

• Visual Studio Add-In：这是一个向导，让用户可以使用C#、VB、C++ ATL 或C++ CLR 创建 add-in 插件。
• Visual Studio Package：另一个向导，让用户可以在C#、VB 和 C++ 之间选择。
• Visual Studio Shell  Isolated：用户用它可以创建基于 Visual Studio IDE 的应用。早期的例子可以参考 AddOn Studio for World of Warcraft。

查看英文原文：InfoQ: Macros Have Been Dropped from Visual Studio 11 （见下文）

Macros Have Been Dropped from Visual Studio 11

Posted by Jonathan Allen on Oct 04, 2011

Sections

   

Development

   

Topics

   

IDE 

Tags

   

Macros , 

Visual Studio , 

Visual Studio 11

Share |

As of version 11, macros will no longer be available in Visual Studio. This marks the first version in nearly a decade to not allow for crating ad-hock extensions to the IDE. Fully compiled extensions can still be created and new project templates are included to make that process much easier.

According to Microsoft's usage tracking data, macros in Visual Studio are currently being used by less than 1% of all developers. This alone isn't enough to cause Microsoft to drop the feature, the macro feature in Visual Studio has also a disproportionately high maintenance cost. Unlike most other features, the macro support has to be updated and exhaustively tested for each new version of Visual Studio. In theory one should be able to record and replay any feature via the macro IDE, which places a huge maintenance burden on Microsoft.

According to Matt Kaufman, the macro IDE hasn't been updated for several versions. Firing it up, one will quickly notice that it looks like an old version of Visual Studio. More troubling is the fact that it still only supports Visual Basic. One cannot use C# or any of the newer .NET languages to create macros.

As mentioned before, the support for extensibility now includes several new project templates. The current list, which is offered under both VB and C# follows:

• Visual Studio Package: This is used for the older VSPackage style pugin-ins.
• Editor Classifier: Used for creating your own syntax highlighting
• Editor Margin: Used to adorn the margins in an editor window
• Editor Text Adornment: Used to adorn text within an editor window
• Editor Viewport Adornment: Used to place editor visuals relative to the editor's visual surface
• [VB/C#] Item Template
• [VB/C#] Project Template
• VSIX Project: This is the newer plug-in model that is most commonly seen in the Visual Studio Gallery
• Windows Forms Toolbox Control
• WPF Toolbox Control

In addition to the language specific templates there is a generic extensibility folder containing:

• Visual Studio Add-In: This is a wizard that lets you create add-ins using C#, VB, C++ ATL, or C++ CLR.
• Visual Studio Package: This is another wizard that lets you choose between C#, VB, and C++.
• Visual Studio Shell  Isolated: This lets one create applications based on the Visual Studio IDE itself. An early example of this is the AddOn Studio for World of Warcraft.

RelatedVendorContent

Extend Visual Studio to Oracle with Toad Webinar

Top 5 Software Development Process Challenges

vFabric: in-memory SQL database

The Agile Tester

Kanban for Agile Teams

2 comments

Watch Thread Reply

Developers are just users, they don't customize by Adam Nemeth Posted 04/10/2011 09:09

Putting this into context by john zabroski Posted 05/10/2011 03:41