Carlos Quintero's blog

Creating toolwindows in Visual Studio .NET 2002/2003 was incredibly difficult because you needed an ActiveX “shim” control to host a .NET (managed) usercontrol. Visual Studio 2005 simplified this a lot using the CreateToolWindow2 function, that doesn’t need the shim control. I have updated completely this article of January 2006 to remove “support” for VS.NET 2002/2003 […]

This problem was reported some weeks ago in the MSDN VSX forum. I was not aware of it before that post so I have documented it today (and fortunately the workaround is easy): PRB: System.NotImplementedException calling EnvDTE.Project.Delete from a Visual Studio macro or add-in. http://www.mztools.com/articles/2011/MZ2011008.aspx

Retrieving a CommandbarPopup in Visual Studio to add buttons has always been tricky. There are incorrect ways to do it: PRB: Performance problem of DTE.CommandBars[name] for CommandbarPopups in Visual Studio 2010 http://www.mztools.com/articles/2011/MZ2011005.aspx BTW, I have updated this popular article to avoid that performance problem in VS 2010: HOWTO: Adding buttons, commandbars and toolbars to Visual […]

While not recommended because there can be two different  commandbar popups with the same name, you could use DTE.CommandBars[commandBarPopupName] to retrieve the commandbar of a CommandbarPopup from the DTE.CommandBars collection. However, the new WPF-based commandbars of Visual Studio 2010 introduce a performance problem when doing it so if the commandbar popup has not been displayed […]

This article documents a small bug of the Visual Studio code model: BUG: EnvDTE80.CodeEvent.Comment doesn’t return “” for C# events without doc comment http://www.mztools.com/articles/2011/MZ2011007.aspx The bug report that I filed to Microsoft Connect is here: https://connect.microsoft.com/VisualStudio/feedback/details/652387/envdte80-codeevent-comment-returns-doc-doc-instead-of-for-c-events-without-doc-comment#details