officedev

Replacing part of Outlook client's window with a custom form

和自甴很熟 提交于 2020-07-09 07:13:17
问题 I am developing a VSTO application for Outlook client. I am trying have my form open in the part of the Outlook client window which is highlighted in red in the following image: I think I can't use the form regions because they replace the view for a single item. So basically what I want to do is opening my custom form (windows or web) in the red area when I click my tool's button on the toolbar. Any ideas how this can be done? 回答1: There are three main ways for displaying your own form there

Replacing part of Outlook client's window with a custom form

纵然是瞬间 提交于 2020-07-09 07:11:01
问题 I am developing a VSTO application for Outlook client. I am trying have my form open in the part of the Outlook client window which is highlighted in red in the following image: I think I can't use the form regions because they replace the view for a single item. So basically what I want to do is opening my custom form (windows or web) in the red area when I click my tool's button on the toolbar. Any ideas how this can be done? 回答1: There are three main ways for displaying your own form there

Howto: Outlook 2016 for Mac - Debugging/View Console Logs in Outlook Add-in

◇◆丶佛笑我妖孽 提交于 2020-01-04 05:15:00
问题 We develop an Outlook app (now called add-in) using html5/js originally for OWA but now it is targeted to all Office Supported Platforms. And indeed, it seems to work on all platforms (ios, safari on mac, windows browsers and outlook) except for Outlook 2016 for Mac . When running inside Outlook 2016 for Mac it behaves very strangely. Not loading half the times, and when loading, it does not work properly. We find it very hard to find the problem. We did not find a way to debug our scripts or

PowerPoint Programming: Indentation with Ruler margin levels not working?

瘦欲@ 提交于 2019-12-24 10:01:02
问题 Recently we upgraded one our PowerPoint addin to support 2007 and 2010. most of the items we were able to port without problem. one problem we have is that indentations doesn't work when create tables or shapes using the addin. for eg: same table gets dropped with proper indentation in 2003 but same thing doesn't get indentation when added to using 2007. below is the code snippet that allows indenting: With PropertyValues.ObjShape.Table.Cell(row, col).Shape.TextFrame.Ruler For rulerCount = 0

setSolidColor throwing unexpected error in Excel Javascript on chart series

流过昼夜 提交于 2019-12-11 16:13:20
问题 The setSolidColor method of the chart series class is throwing an error in Excel 1907 Build 11901.20080 but NOT in Excel 1902 Build 11328.20116. To demo the error I modified the examples in Script Lab, specifically the section under "charts" called "Create Charts - Create column clustered, line, ...". The data setup is required, here is the code from Scirptlab. This doesn't demo the error just sets up the data. async function setup() { await Excel.run(async (context) => { context.workbook

Expose VSTO functionality to VBA w/o local admin

半腔热情 提交于 2019-12-07 19:47:50
问题 What would be the best way to expose certain functionality in a Dotnet VSTO Excel add-in to VBA, without requiring the user to be a local administrator (i.e. no COM registration, no HttpListener)? Would it be possible to use Microsoft Message Queues from VBA? 回答1: If I may interpret your question as broadly as "How do I expose functionality in a .Net assembly to Excel without COM registration" then an excellent solution is to use Excel's XLL interface. Basically one deploys an xll shim and an

Expose VSTO functionality to VBA w/o local admin

你说的曾经没有我的故事 提交于 2019-12-06 08:15:25
What would be the best way to expose certain functionality in a Dotnet VSTO Excel add-in to VBA, without requiring the user to be a local administrator (i.e. no COM registration, no HttpListener )? Would it be possible to use Microsoft Message Queues from VBA? If I may interpret your question as broadly as "How do I expose functionality in a .Net assembly to Excel without COM registration" then an excellent solution is to use Excel's XLL interface. Basically one deploys an xll shim and an associated .Net dll. When the xll is loaded it reflects over the dll and exposes the functions therein to