I know that the Office Ribbon has gone under pretty significant changes since 2003 and I've done some modest customization of the ribbon in 2010.
Question: I've seen a number of references to .Net and specifically C# and the Office Ribbon. Is this largely just (maybe) dynamic customizing? I mean, Office 2013 can't run any .Net code, can it? At the end of the day, it is still VBA no?
Thanks
I imagine that you are referring to the Ribbon WPF control, documented here: https://msdn.microsoft.com/en-us/library/ff799534%28v=vs.110%29.aspx
This is a UI control that can be used in custom .NET applications, giving them the look and feel of office applications.
If you are referring to the ribbon in actual office applications- as the comments mention, addins can be written in .NET code (this has been possible for quite some time, actually), and these can modify the toolbar. Links are available at the bottom of the page linked above.
Related
It's my first time developing add in for outlook.
I saw that there is a way to develop add in in web technologies such as Angular, React, etc. This add in will work both on older version and new version of outlook?
If I want to develop also for Outlook 2007 | 2013, will add in developed in react will still work?
Another question I had, my add-in should change the current views
I want to add small marks on appointment on the calendar view (see the coloured dots on the meetings)
Add some insights in appointment invitations
Add custom field to new appointment form
I tried to look for solutions that change the views but found only solution that add custom forms and not changing the current form.
Is it possible?
Thanks!
Outlook add-ins are supported in Outlook 2013 or later for Windows, Outlook 2016 or later for Mac. More on Supported hosts.
You will be limited to the certain Extension points. Extension points are the ways that add-ins integrate with Outlook. There is no way to customize Outlook interface with the add-in, instead you will be given the aria (pane, dialog) where you going to display your own UI and communicate with a form to enhance user experience.
If you need to support older Outlook clients and custom forms, you should stay with VSTO technology. Read more on ... How are Office Add-ins different from COM and VSTO add-ins?
Good morning,
my company is looking for a solution in order to distribute an add-in for Outlook 2013 that add a button in the ribbon. I want to create an add-in for Outlook 2013 and I saw that is possible using Visual Studio (I use VS 2013 or 2010) but I don't understand how to add a button in the ribbon (in particular in Home section) and execute a macro when I click on the button (the macro is already created). I read this tutorial https://msdn.microsoft.com/en-us/library/cc668191.aspx and this worked. Someone can help me with some piece of code(c#)?
Thanks for your help
VSTO provides two main ways for customizing the Ribbon UI:
Using the Ribbon designer. See Walkthrough: Creating a Custom Tab by Using the Ribbon Designer for more information.
Using the Ribbon XML markup. See Walkthrough: Creating a Custom Tab by Using Ribbon XML for more information.
You need to specify the idMso attribute of the built-in tab if you need to add your custom controls there. See Office 2013 Help Files: Office Fluent User Interface Control Identifiers for control IDs.
Finally, I'd suggest moving your VBA macro to the add-in. It will improve the overall performance and allows to use the BCL classes (a wide varioety of controls and components) for getting the job done. Moveover, you will be able to deplay the add-in easily. VBA macros are not designed for deployiong on multiple PCs.
I require assistance for the following
I would like to create an add-in for Microsoft Visio 2010 to zoom individual shapes. To achieve this I would like to create a TreeView (using Visual Studio 2010). From this control, based on the selection, either zoom the entire diagram or individual shapes.
I have tried custom task panes but its not possible for Visio to extend custom task panes.
Any suggestions are most welcome.
Been a long time since I've done an addin for Visio, but you may have luck checking here. Go down where it says "Managed Code".
Here is some more info: Overview of Add-ons and COM Add-ins in Visio 2007
and another related answer: how to develop an add-in for visio
I have looked at several tutorials on writing general Outlook add-ins, and have gotten simple examples to work: items in menu, context menu, ribbons, etc.
Many of Microsoft's documentation has send me in circles, or is in VB, so I have run into some questions with what we are trying to accomplish.
Is there a way to add a custom control below the Subject line in a new email? We need to supply a drop-down and add an additional header to emails sent for email tracking. Right now the best I have gotten is adding a CommandBarButton in the "Add-ins" tab of the Ribbon, is there a better method?
Will we run into any issues installing for multiple versions of outlook? (Will only 2007 and higher work?)
Can you host WPF controls directly in a Ribbon, etc.? I know that WPF popup windows work just fine when shown from a CommandBarButton.
Are there some good links out there for what we're trying to do?
2: Multi-version support is a PITA. The hedge-your-bets approach is to develop on a PC running the version of Outlook you want to support; thus you may have multiple setup packages for each supported version. Everybody tries to get around this though, but I've used this approach with success:
Version-Specific UI in Add-ins - Andrew Whitechapel - Site Home - MSDN Blogs:
http://blogs.msdn.com/b/andreww/archive/2008/09/02/version-specific-ui-in-add-ins.aspx
4: Essential resources:
Visual Studio Tools for Office For Office and Outlook for Developers Forums on MSDN
OutlookCode.com
(FYI, I work for Add-in Express)
No, not without implementing the entire message window.
We have to make 2 projects for 2007 and 2010, we are skipping 2003 and below b/c it is much more difficult and would be rarely used.
Can't host WPF in a Ribbon, we're going to display a WPF popup from a Ribbon button press.
Best thing I've found is to just follow the project template in Visual Studio and mess around.
Overall, our add-in is going to do the following:
Make 2 projects for 2010 and 2007 that share a "Shared" assembly
All reusable work is done in the shared assembly
WPF is only displayed via popup windows (you can do a custom task pane, but it doesn't make sense for our add-in)
Is there a way to disable to Application Menu, the circle thing on the left hand corner, so the user can't click on it?
I have absolutely no use on that, and cannot think of anything I can use that, I can't find any options to disable it.
Please help
Many thanks
I did something like this, and managed to remove the Application Menu. Do check if this is the way you wanted it to be.
<r:Ribbon.ApplicationMenu>
<r:RibbonApplicationMenu Visibility="Collapsed" >
</r:RibbonApplicationMenu>
</r:Ribbon.ApplicationMenu>
In to xaml file post the code:
<Ribbon ApplicationMenu="{x:Null}">
<TabControl></TabControl>
</Ribbon>
I believe that would go against the Microsoft license for using the ribbon interface.
Check it out here: http://msdn.microsoft.com/en-us/office/aa973809.aspx (dead)
(Archive from 2012-09-11)
Office UI licensing for developers
Overview
The Office UI licensing program is designed for software developers
who wish to implement the Office UI as a software component and/or
incorporate the Office UI into their own applications.
A license to use the Microsoft-claimed intellectual property in the
Office UI is required when the software developer does not use one of
the Microsoft-provided implementations of the UI that carries a
separate license (currently either the Microsoft Windows 7 API
implementation or the Microsoft WPF implementation in the .NET
framework 4).
A license is also required when the software developer wishes to use
elements of the Office 2010 UI that are not provided by those other
implementations.
How to implement the Office UI in your own software
There are currently three primary categories of ways for a software
developer to implement the Office UI in their own application or
component.
Use the Microsoft Windows 7 Scenic Ribbon implementation
Details about the Scenic Ribbon can be found on the MSDN Code Gallery. Use of
the Scenic Ribbon implementation is governed by the Microsoft Windows
SDK EULA and does not require a developer to accept the terms of the
Office UI license on this site.
Use the Microsoft Ribbon for WPF Implementation
Details about the Microsoft Ribbon for WPF Implementation (delivered via MS Downloads)
can be found in the MSDN Library. Use of the Microsoft Ribbon for WPF
is governed by a EULA similar to that of the .NET Framework. This
release does not require developers to accept the terms of the Office
UI license on this site.
Use Microsoft Foundation Classes (MFC) Ribbon, build it yourself, or use a third-party component
All of the options in this category
require acceptance of the Office UI License terms on this site. The
additional benefits of this category include the ability to implement
across more platforms, the ability to use elements of the Office 2010
UI that are not incorporated in the other implementations, and the
ability to use a third-party component that may have other benefits to
you as a developer.
If you find this category appropriate you should read the materials
on this site, specifically the Office UI License and the Office UI
Design Guidelines. You may search the web for component vendors by
searching for terms like "Microsoft Ribbon component vendor".
But I don't have any use for it either, so I just put the "Exit" option in there.
EDIT:
It was confusing if the Application Menu required only in the IMPLEMENTATION of the control, or do you have to USE IT in all applications that use a ribbon?
Some things are clear like: You HAVE to have a "Home" tab, and when the application starts, it HAS to be the selected tab (just like in Office 2007.) But some other things... Kind of a guessing game.
I just sent the Office UI group at Microsoft an e-mail asking for some clarification on this. Here's the answer: looks like the Application Menu is NOT optional:
Thank you for submitting your question. The design guidelines do
stipulate that the Application Menu is required and it is a critical
element of the Ribbon UI implementation. Different control sets may
allow for the hiding or disabling of the UI element, but the
expectation is that your finished application will still contain an
Application Menu element (you may seek to implement it yourself as
part of your window frame, or through other means).
EDIT: The license has been retired:
https://law.stackexchange.com/questions/18329/what-is-the-status-of-microsoft-ribbon-licensing-as-of-2017
this.ultraToolbarsManager1.Office2007UICompatibility = false;
this.ultraToolbarsManager1.Ribbon.FileMenuStyle = Infragistics.Win.UltraWinToolbars.FileMenuStyle.None;
Try this one. its Only used windows application form