Home Dashboard Directory Help
Search

Custom pictures in CommandBarButtons created by add-in don't show a transparent background by Carlos J. Quintero


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 461192
Opened: 5/29/2009 4:42:53 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Custom pictures in CommandBarButtons created by add-in doesn't show a transparent background when using RGB=0,254,0 (almost pure green) as background color.

Details
Sign in to post a comment.
Posted by Microsoft on 7/31/2009 at 11:51 AM
Hello Carlos,

Good news - Jeff has just checked in a fix for this bug, and you should see the results of this fix in Visual Studio 2010 Beta 2. I'm going to send this bug on to QA for verification and final sign-off.

Thanks,
Suzanne Hansen
Program Manager, Visual Studio Platform Shell
Posted by Microsoft on 6/30/2009 at 2:48 PM
Thanks. I'll notify the dev of this update while he is investigating the issue.

Thanks,
Visual Studio Platform Team
Posted by Carlos J. Quintero on 6/25/2009 at 3:52 AM
UPDATE: I have realized today that you are following the Microsoft Visual Studio 2010 User Interface Guidelines (http://code.msdn.microsoft.com/VS2010UX/Release/ProjectReleases.aspx?ReleaseId=2743):

"Even though high-color has been around for many years now, we still need to work to remove these historic hacks and assumptions."

It seems so because you have removed support for RGB=0,254,0 as background color (the bug that I am reporting) and now you support 32-bit bitmaps with alpha channel for add-in commands in VS 2010 Beta 1 (the thing that I have realized today that it works, something that didn't work in previous versions).

Notice, however, that .NET 2.0 add-ins targeting VS 2005/2008/2010 with the same satellite Dll will need to supply two sets of bitmaps: one with RGB=0,254,0 for VS2005/2008 and another with 32-bit bitmaps for VS 2010. While it is really great to move to 32-bit bitmaps, it would be good to support RGB=0,254,0 too for one or two releases for backwards compatibility, given that most developers of commercial add-ins will want to support the previous two releases or so...
Posted by Microsoft on 6/19/2009 at 1:40 PM
Thanks CarlosQ for attaching the add-in. I wanted to confirm that we've received the file and that Jeff is still investigating this bug.

Thanks,
Suzanne Hansen, Program Manager, Visual Studio Platform Shell Team
Posted by Carlos J. Quintero on 6/12/2009 at 4:23 PM
I have attached an add-in created with VS 2005 (you can use VS 2008 if you want) and a managed (not C++) satellite DLL. The add-in adds a button to the right of the "Standard" toolbar. Put the .AddIn file in the proper folder for VS 2005 to recognize it and load the add-in in VS 2005 and see that the picture of the button (a blue square) has transparent background.

Now, put the .AddIn file in the proper folder for VS 2010 Beta 1 to recognize it and load the add-in in VS 2010 Beta 1. Notice that the picture has a green background rather than transparent.

To cover all bases, now convert the add-in to COM-addin (rather than XML-add-in) and a satellite DLL in C++ with the same bitmap. Register the add-in with regasm.exe /codebase and register the add-in within Visual Studio using the Windows registry (and use the SatelliteDLL and SatellitePath registry entries required for native satellite DLLs).

In both cases, the bitmap (either in native or managed satellite DLL) using as background the color RGB=0,254,0 (almost green) should show transparent background, but only VS 2005 (or VS 2008) shows the transparent background. VS 2010 shows green background.
Posted by Microsoft on 6/11/2009 at 4:43 PM
Hello CarlosQ,

Thank you for reporting this issue. Would you be able to provide a sample project or code illustrating the calls you are making when reproducing this issue? I want to make sure I'm covering all of the bases when I fix it.

Thank you,
Jeff Robison
Senior Developer, Visual Studio Platform Shell
Posted by Microsoft on 6/1/2009 at 2:32 AM
Thanks for your feedback. We are escalating this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 5/31/2009 at 3:46 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.