Walkthrough: Extending VS 2010 to Support Additional Programming Languages

Walkthrough: Extending VS 2010 to Support Additional Programming Languages

  • Comments 10

The Visual Studio team has sponsored a set of Visual Studio Extensibility walkthroughs that will be hosted on www.devx.com.  The first walkthrough showed how to write a blogging extension for VS 2010 and demonstrated the basics of VSPackages, Commands, Tool Windows, and MEF.  In this walkthrough, Steve Apiki shows you how to extend the Visual Studio 2010 editor to support your custom language.  He walks you through how to add Syntax Highlighting, Error Tags, Quick Info tool-tips and Statement Completion using the new MEF (Managed Extensibility Framework) extensibility points in the Visual Studio 2010 Editor.

Check it out and let us know what you think!  Also, if you have ideas for other articles you would like to see, please leave a comment.

Leave a Comment
  • Please add 4 and 2 and type the answer here:
  • Post
  • I developed a plugin for VS2008 & VS2010 that let the user tweet from within the VS's Code Editor, but Id never found an example that let me use the  Intellisense/autocomplete feature in my plugin.

    I guess that would be cool if you post an example about that!

  • Here's my plugin: procrastinationkit.codeplex.com

  • Can someone write a plug-in so VS2010 will support Visual Basic 6? I'm stuck with this legacy code because we don't have time to port to VB.Net and the IDE is awful, especially in Win7.

  • Do this feature allows us to support debugging as well?

  • @JLuis - there is a new walkthrough just published by the same author that deals with auto-completion in the editor at www.devx.com/.../45058

  • I have problems when I try to convert from VC++6.0/7.0 to VC++10.0. I have a solution with several project that generate lib files. Those are then linked together with the main routine to build the exe. With 6.0 all projects generating libs were automatically included in then linking phase so that there was no need to enter complex lib file paths to the linker. Now with the 10.0 this feature is missing??!! The IDE does not find the libraries even if the debendeces are correctly given??

    MS People. Do you know that the VS2010 serial key is already known by 65 million computers (in the P2P eMule network)? There is a text file floating around called

    "Visual Studio 2010 all Editions.txt"

    with the contents:

    "Valid Product Key of Visual Studio 2010 all Editions

    Y......"

    Maybe also visit the following link and find it there also!!

    www.celebwebnews.com/.../leaked-valid-master-product-key-of-microsoft-visual-studio-2010-ultimate-premium-and-professional-edition.html

    I think those keys and protection methods are already lost forever. I have nothing to do with those people and I am using a legal copy of your product. I just don't understand why they have to broadcast the keys if they managed to crack them and create damage!?

  • I have problems when I try to convert from VC++6.0/7.0 to VC++10.0. I have a solution with several project that generate lib files. Those are then linked together with the main routine to build the exe. With 6.0 all projects generating libs were automatically included in then linking phase so that there was no need to enter complex lib file paths to the linker. Now with the 10.0 this feature is missing??!! The IDE does not find the libraries even if the debendeces are correctly given??

    MS People. Do you know that the VS2010 serial key is already known by 65 million computers (in the P2P eMule network)? There is a text file floating around called

    "Visual Studio 2010 all Editions.txt"

    with the contents:

    "Valid Product Key of Visual Studio 2010 all Editions

    Y......"

    Maybe also visit the following link and find it there also!!

    www.celebwebnews.com/.../leaked-valid-master-product-key-of-microsoft-visual-studio-2010-ultimate-premium-and-professional-edition.html

    I think those keys and protection methods are already lost forever. I have nothing to do with those people and I am using a legal copy of your product. I just don't understand why they have to broadcast the keys if they managed to crack them and create damage!?

  • @AdityaReddyM - This article is mostly about extending the editor. Documentation about debugger extensibilty can be found starting at msdn.microsoft.com/.../bb161718.aspx.

  • @Gary - Tnx sooo much :D let my check it

  • What has happened to these tutorials? If I try to open the links, I'm getting redirected to the DevX main page.

Page 1 of 1 (10 items)