Browse by Tags
All Tags »
VS 2010 (
RSS)
There is a bug/issue that I reported years ago for VS 2005 and was not even acknowledged as a bug but "by design". VS 2010 (Beta 2) still exhibits it so I keep pushing to get if fixed (the original bug report was lost, I think it died when MSDN...
In VS 2008 (and previous versions), when you opened the "Tools", "Customize..." dialog, "Commands" tab, you got a list of "categories", and each category has a list of commands that you could drag and drop on some...
In the post CommandBarButton.Mask property deprecated in VS 2010 I mentioned that VS 2010 will deprecate the Mask property of CommandBarButton to specify bitmap transparency, accepting 32-bit bitmaps with transparency in the alpha channel in the CommandBarButton...
Back in VS.NET 2002/2003 the only way to change the style (Icon only, or Icon + Caption) of a CommandBarButton created from a Command was to cast the CommandBarControl returned by Command.AddControl to CommandBarButton and use the CommandBarButton.Style...
This one happens when an add-in: - Creates a temporary toolbar using CommandBars.Add - Creates a temporary CommandBarPopup on that toolbar - Creates a command and tries to add a CommandBarButton from that command to that CommandBarPopup using Command...
After 3 hours isolating this to the minimal expression (which is tedious if your add-in is has lots of user interface items and debugging a VS 2010 add-in on a virtual machine is painfully slow), here it is: VS 2010 Beta 2 Bug: deleting a CommandbarPopup...
I can't express how disappointed, frustrated (and more things!) I am with VS 2010 Beta 2 regarding correct behavior of commandbars for add-ins. It seems that once a bug is fixed in a VS 2010 build and an add-in can pass that point, new bugs surface...
Microsoft has reported that this problem will be fixed: " 'Object must be the same type as the enum' exception calling CommandBars.Add from an add-in" http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=462766...
FWIW, I have verified that VS 2010 Beta 2 certainly fixes the issue of supporting RGB=0,254,0 for transparent color in 24-bit command pictures that I mentioned here . So, if your add-in targets VS 2005, 2008 and 2010 you can use that color for the transparent...
This is going to be messy, so step by step: Imagine that you are developing an add-in that uses a temporary user interface (not permanent one) , and creates a couple of commandbars of kind "toolbar", and many commandbars of kind "popup"...
If you are testing your add-in with the recently released VS 2010 Beta 2 chances are that you have noticed that the new WPF-based commandbars, buttons and icons are not yet ready for prime time. It seems that my MZ-Tools add-in uses every possible method...
If you are developing add-ins for in-house use, chances are that you can drive, encourage or even force the whole organization to use the latest version of Visual Studio and therefore your add-in needs to target only that version. But if you are developing...
As you know if you develop add-ins, Visual Studio 2005 introduced XML-based add-ins that use an .AddIn file that you must place in the proper folder for Visual Studio to show the add-in in the Add-In Manager . Which XML parser Visual Studio uses to parse...
As you already know from my posts in the last months, VS 2010 will use WPF-based commandbars and will introduce support for 32-bit bitmaps with built-in transparency in the alpha channel for pictures of commands of add-ins, apart from the old way of using...
The problem that always existed in Visual Studio with the generated grayscale picture for a disabled command of an add-in (or CommandBarButton without a command) is going to be fixed in Visual Studio 2010, according to the tests that I have done. That...
In my last post Visual Studio 2010 getting rid of satellite DLLs for add-ins I mentioned that VS 2010 will provide two approaches to avoid satellite DLLs for command pictures of add-ins: The first one was clear: command pictures will be able to be embedded...
After four years since I started pushing Microsoft to get rid of satellite DLLs to provide custom pictures for commands of add-ins , and then pushing again and then even again , and even through private channels I have as an MVP and even through private...
My post of a week ago " Microsoft no longer fixing (small) bugs for VS 2010, now focusing on stabilization and performance " has been commented (see the Comments section) by the DJ Park (C# IDE, Program Manager) explaining that the three bugs...
The issue that I opened about VS 2010 Beta 1 command pictures supporting for the first time 32-bit bitmaps with alpha channel for transparency but not RGB=0,254,0 as in previous Visual Studio versions has been resolved by Microsoft for Beta 2: Custom...
Although VS 2010 Beta 2 hasn't been released yet, Microsoft has stopped fixing the certainly minor bugs that I have reported in the last days about the C# file code model. Instead they are currently focused "on stabilizing and improving the performance...
More Posts
Next page »