I have received several bug reports in the last years about MZ-Tools for Visual Studio .NET that after some investigation I have discovered that the bugs only happen when certain 3rd party add-in or package is installed, or even not installed. For example, this one only happens when CodeRush is installed . And this other one only happens in VS 2008 if the Code Analysis Tools are not installed. And I have found another ones that I have not even documented in this blog, just patching my code to prevent

When I thought that I have fixed the bug that I explained in my last post , I found another subtle one: in VS 2010 and 2012, setting to False the Visible property of a CommandBarPopup was not honored if the CommandBarPopup was created on a context menu (for example, in the Code Window context menu), but it worked if created on a Toolbar (for example, the Standard toolbar). This is another bug introduced in the WPF-based commandbars of VS 2010, since it works as expected in VS 2008 and before. Unfortunately

A couple of days ago a customer of the new version MZ-Tools 7.0 for Visual Studio reported a bug regarding the dropdown menus visibility not preserved across Visual Studio sessions . I isolated the bug which happened to be a bug in the WPF-based commandbars of Visual Studio 2010 (and 2012), not happening in VS 2008 and before. I have written a small article to document it: BUG: CommandbarPopup.Caption changes CommandbarPopup.CommandBar.Name and viceversa. http://www.mztools.com/articles/2012/MZ2012007

I have got a new laptop (an Apple MacBook Air 11") and after installing BootCamp, Windows 7, VB6, VS 2005, 2008 and 2010, yesterday I noticed that when loading MZ-Tools 3.0 for VB6 , it prompted to repair Visual Studio 2010. I had received the same or similar issue from 2 or 3 users these last years that I never knew how to solve, so I could only recommend to repair or reinstall Office, VB6 ,etc. Today I have investigated more and it seems that there are multiple causes but one of them documented

After exactly 5 years (an eternity) since the last major version, today finally I have released a new major version of MZ-Tools, version 7.0: http://www.mztools.com/ This new version not only adds support for Visual Studio 2012 (which Microsoft has just announced also today that will be available on August 15 ), but on the contrary to MZ-Tools 6.0 (which had the same feature set than MZ-Tools 2005 and MZ-Tools 4.0, just adapted to the new versions of Visual Studio), it adds new features and enhancements

If Monty Hammontree and his team continue to ignore the community feedback like so far , this is the macro that you need to fix the ALL CAPS of the main menu of VS 11: Sub NoALLCAPS() Dim commandBar As Microsoft.VisualStudio.CommandBars.CommandBar commandBar = CType(DTE.CommandBars, Microsoft.VisualStudio.CommandBars.CommandBars).Item("MenuBar") For Each control As Microsoft.VisualStudio.CommandBars.CommandBarControl In commandBar.Controls control.Caption = StrConv(control.Caption, VbStrConv

My MZ-Tools add-in was experiencing a random "System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component." when using the EnvDTE.DTE.ActiveSolutionProjects property that I knew that other developer reported in the MSDN VSX Forum in January . Today I tested a guess of Ryan Molden (from Microsoft) in his answer about a dependency on the visibility of the Solution Explorer and he was right. But when I was writing the corresponding

Since my laptop has several software issues that will require a fresh installation at some point in the near future, I decided to install VS 11 Beta side by side with VS 2010, and one thing that I noticed the other day was that my MZ-Tools add-in, when loaded in VS 2010, was showing gray pictures (rather than color pictures) for controls of the System.Windows.Forms namespace in some of its features. Yesterday I decided to investigate the glitch and I noticed that the Document Outline built-in toolwindow

The approach that I described in the following article to use a single satellite Dll with the "en-US" culture using the AppDomain.AssemblyResolve event doesn't work in VS 11 Beta: HOWTO: Create a command with a custom picture using a managed satellite DLL for a XML-based Visual Studio add-in. http://www.mztools.com/articles/2012/MZ2012002.aspx I have just opened a bug report at Microsoft Connect: VS11 Beta does not raise AppDomain.AssemblyResolve to receive the satellite dll in add

This one that I mentioned in my last post that I would investigate has been extremely easy: HOWTO: Create a command with a custom picture using an ImageList for a XML-based Visual Studio add-in. http://www.mztools.com/articles/2012/MZ2012005.aspx And Microsoft updated correctly the documentation for Visual Studio 2010 regarding the new possibilities of the Bitmap parameter of the EnvDTE80.Commands2.AddNamedCommand2 method: EnvDTE80.Commands2.AddNamedCommand2 http://msdn.microsoft.com/en-us/library