Friday, October 23, 2009

How to identify menus and commands with Visual Studio?

Sometimes when we extend the Visual Studio it's very important to know what IDs the menu or command has. Ed Dore published great post Using EnableVSIPLogging to identify menus and commands with VS 2005 + SP1, which describes how to enable VSIP (the old abbreviation of VSX) logging.

To do that all you need is to add(or change) the setting in Windows Registry that informs IDE to enable logging. That is the registry file content for Visual Studio 2005 SP1 or above:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\General]
"EnableVSIPLogging"=dword:00000001

Similar registry file will work for Visual Studio 2008 as well:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\General]
"EnableVSIPLogging"=dword:00000001

Once "EnableVSIPLogging" setting is set to 1, you can click on menu or command with CTRL+SHIFT pressed to see the information about clicked item in message box like this:

VSDebug Message box for Format Document toolbar button

Look to Ed Dore's post for more details.

Keep in touch and happy extending!

Read more...

Tuesday, October 20, 2009

Beta Visual Studio 2010 and .NET Framework 4 released!

On 21 October developers can try new possibilities provided by Visual Studio 2010 Beta 1 and .NET Framework 4.0!

The most important things:

  • Top testing possibilities
  • IDE improvements
  • New drag-and-drop data binding mechanism for Silverlight and WPF
  • Development tools for Windows 7, SharePoint and other technologies
  • New integration possibilities with such technologies as: ASP.NET MVC, UML, Expression, multi-core and database

Read more about and download new Visual Studio 2010 Beta 1 here: http://www.microsoft.com/visualstudio/en-us/products/2010/default.mspx

Keep in touch and happy extending!

Read more...