Hello, I’m Pat Brenner, a developer on the Visual C++ Libraries team, and I primarily work on MFC.
In Visual Studio 2010, a ribbon designer was added which allows you to visually edit the ribbon used in your MFC application. This doesn’t help you, however, if you adopted the ribbon user interface with Visual Studio 2008 SP1 and you’re creating your ribbon UI entirely with code in your application. We did consider that scenario, however, and added functionality to MFC to allow conversion of a “code” ribbon to an XML ribbon resource. I’ve been meaning to post an article on how to do this, so here it is.
I’ll use the conversion of the ribbon in the MSOffice2007Demo sample as an example:
I hope you find this information helpful.
Pat Brenner Visual C++ Libraries Development
Thanks for the info. I want to migrate several projects
from Visual C++ 6.0 to VS2010 that link to the MFC
statically, and don't use any of the Feature Pack classes
and when are compiled in VS2010 the size of the executable
increases significantly. I also have other projects using
the BCGSoft classes and they overlap with the feature
classes: Currently, I prefer to use the BCGSoft classes
because it is possible to enable the Visual Themes in the
FormView classes something that is not implemented yet in
the Feature Pack classes.
It would be useful then, if we have an option to exclude all
of the Feature Classes from the executable when statically
linking applications that don’t use the Feature Pack or when
using the BCGSoft framework.
That is nice. Thanks for sharing.
@Marcello: We are working on the static link size issue and are confident that we will have a fix for the next major version that addresses the size increase of applications that are not using Feature Pack controls.
OK. Thank you. I think the Feature Pack is a valuable addition but we should be able to build small executables as in the earlier releases of Visual Studio.