Gaston Milano's WebLog

I'm in Redmond now and yesterday I met some old friends ;)

I added 2 new commands in the context menu on  text editors:  (They are included in the whidbeycommand 2.1 setup)

I have uploaded a new setup for the whidbeycommands (close all but this, copy full path and view file in explorer). This new setup fix some installation problems and you don´t need to run devenv /setup anymore.

You can download the VSIP SDK 2005 from

I successfully compiled a solution with 36 C# projects and 14 C++ (Managed, libs, etc), I did try the same thing with earlier Whidbey bits and I had failed.

After I developed a language service with babel, I noted that when you are
 in a file that use this language service, the SearchCombo (Find combo) is
 empty, the same happen with  configurations combo. I was trying to fix
 this problem and finally I found the cause of the problem. In the babel
 package in the ViewFilter.cpp there is an error.
 In the execute method

 STDMETHODIMP ViewFilter::Exec(in const GUID* commandGroup, ....., out
 VARIANT* result)
 {
     if (result) VariantInit(result);
         ....
 }

 If you comment the "if" statement everything start working
 The problem is that the ViewFilter can't initialize this variant always,
it should initialize the result only if it handle the command, because it is
in  a message chain.

 Now my problem is how to distribute my babel package, I don't wanna change
 the guids only for this fix, may be in the site the VSIP Team could upload
a new merge module for babel with fixes.

Sometimes is necessary to change the text for a menu item depending on the selection.  In order to do that you have to do 2 things:

This is a sample of using Automation on a VSIPExtras package.