Currently we developed a VB macro for word. While we tried to use it on mac it failed with message "VB Macro not supported in mac".
Is there a way to c# office add-in for mac?
My requirement is to have a simple utility to add comments(read from user) to the selected text in the current word document. Also need the functionality of the OpenFileDialog.
Mac Office does not (i.e. no longer) support COM/VBA automation. This means that you won't be able to use code from your existing Windows add-in.
In order to automate Mac Office you would have to make use of Automator Actions. I am not very familiar with these, but I believe that they are less feature-rich than the VBA object model of the Windows edition.
The following page has some Actions to get you started:
Microsoft Office Automator Actions
Update: It seems that the new Mac Office 2011 comes again with some support for VBA automation.
Related
I am trying to develop an Add-In for Microsoft Word on macOS. The Windows version of the Add-In is already in development, but I don't have access to its source code. It seems like the following is the 'landing' page for developing Add-Ins for Office:
https://learn.microsoft.com/en-us/office/dev/add-ins/
The above documentation seems to say that Add-Ins have to developed using web-technologies, and, upon examination of existing, Third-party, Add-Ins, this seems to be the case at least for the UI. What I don't understand, is, if the entire plugin has to be written using web-oriented languages, or if there is a macOS oriented SDK that allows to implement at least the underlying logic using a macOS native SDK, perhaps using Objective-C or Swift. I was hoping that somebody more expert could bring me in the right direction. Thanks for your attention.
There is no platform specific SDK for developing Office add-ins. You can use web technologies for developing cross-platform Office add-ins, see https://learn.microsoft.com/en-us/office/dev/add-ins/overview/office-add-ins for more information.
You also can use AppleScript for automating tasks in Word on the MacOS.
The problem:
I have a feature for a Microsoft Outlook web add-in which works fine in Office 365 Outlook, but when I test the same feature on Outlook for Mac or Outlook for Windows, the same feature doesn't work. The web add-in still installs fine on Outlook for Mac, it's just that there is a discrepancy between the behavior I am seeing on Office 365 Outlook and Outlook for Mac (this is also true when testing on Outlook for Windows, which has the same behavior as the Mac version).
What I've tried (Mac): I've tried running defaults write NSGlobalDomain WebKitDeveloperExtras -bool true as suggested from this answer and defaults write com.microsoft.Outlook OfficeWebAddinDeveloperExtras -bool true as suggested here and have an option to View Source which opens the HTML source in what appears to be a TextEdit window, but I'm still unable to inspect element in order to see any errors.
What I've tried (Windows):
I've tried using the VSCode Debugger Extension for Office Add-Ins to try to attach the debugger to Outlook for Windows, but keep running into this 'Error processing attach' error.
Additional Notes:
On Mac, I'm running Microsoft Outlook for Mac version 16.43 on MacOS Catalina version 10.15.6 and on Windows I'm running Outlook on Windows 10 Pro version 1909 inside a VM.
My understanding is that while debugging web add-ins for Word, Excel, and PowerPoint are all pretty well supported, debugging add-ins for Outlook on Mac or Windows is somewhat limited at the moment. Has anyone had success in debugging Outlook web add-ins running on Outlook for Mac and/or Windows?
For Outlook for Mac, we think this is specific to the Mac App Store build of Office, which currently doesn't support those flags. To workaround this, you will need to get a non App Store build. You can get one by signing up for the developer program and getting a tenant: https://aka.ms/o365devprogram. (similar issue: https://github.com/OfficeDev/office-js/issues/506)
For Outlook for Windows, we suggest attaching a debugger. Instructions for how to attach a debugger can be found here. Note that there is a different debugger for add-ins that run in Edge and IE.
I am not able to identify UI controls of Windows Store apps using AutoIt Window Information Tool. The standard app Calculator for example (Windows 10):
As you can see, it doesn't show information for button 8. I tried both x86 and x64 versions.
How to interact with Windows Store apps? For traditional desktop apps AutoIt works as expected.
It's impossible, AutoIt developers have no plans to support UI Automation API. You can find Inspect.exe in your Windows SDK and run it in UIA mode to compare with AutoIt Info tool.
There are some other tools supporting UIA (TestStack.White (C#), Winium.Desktop (C#) and some direct UIA wrappers on other languages like pyuiautomation on Python). pywinauto 0.6.0 added MS UI Automation support.
UIA support for AutoIt; 24 Apr 2009 AutoIt forum thread. Plans may have changed, but it's the top result for a "AutoIt WPF support" Google search.
In order to use Autoit Window info tool in Win10 you should use 64bit version exe.
Au3Info_x64.exe
Common location is C:\Program Files (x86)\AutoIt3\Au3Info_x64.exe
In my company we have an existing product that runs on Windows 7 and communicates with our web services.
We wish to make a Windows 8 tablet version of our product, and my first thought was:
"Hey, its just a new Windows version, so we can probably use our existing model, data access and business layer logic projects, and just focus on making a new UI layer"
But I fear that this is not the case, or am I wrong?
I tried opening our VS2010 solution file in VS2012 Express, but received an error "This edition of Visual Studio only supports Windows Store apps".
So, my naive hope now is: Can anyone tell me the easiest way to make our existing code work in a Windows 8 App?
EDIT:
The code is .NET C#, and my thought was that I just wanted to make a Windows 8 app so that the product had a tablet/touch friendly interface.
In general, you'll make a new UI using XAML, reuse a lot of your existing code, and change the data access to use SQLite.
VS2012 Express Edition is for making Windows Store apps. By "Windows Store" app, I mean an app which uses the WinRT APIs. Depending on your code, making a Windows Store version of your app can be straightforward.
If you need other features, you might need a different version of Visual Studio 2012. You definitely need to be on 2012 though. You can't build a Windows Store application with Visual Studio 2010. I think you know this already though.
If your existing .NET app uses WPF for the UI, you can reuse a lot of your XAML knowledge for the Windows 8 port. It's not as simple as recompiling, but it should be straightforward.
SQL CE is currently not an option for Windows Store applications. Instead, consider using SQLite.
Take a look at a post on MSDN called .NET for Windows Store apps - supported APIs. Some APIs you may be familiar with have been moved to WinRT. Sometimes porting is as simple as changing namespaces.
You mention that you also write to the C: drive. There's a sample on MSDN on how to read and write files.
So You need to build a new Metro Style Interface.
Wen You built interface just copy the Logic of your old application.
You can open old application in old VS 2010 and copy code line by line.
You can't convert old Windows app to Metro Style App.
I have PowerPoint 2008 running on my Mac. Is there a way to navigate, like forward and backward, the PowerPoint presentation using some program in Python, Java, C/C++ or other language?
Yes, using Applescript. If you can't script Powerpoint directly (look in its script Library using the editor) you can send keypresses to it using the accessibility framework.
AppleScript. There are some examples here: http://www.mactech.com/articles/mactech/Vol.23/23.03/23.03AppleScriptPowerPoint/index.html. Unfortunately, all of the Mac Office 2008 VBA to AppleScript samples have been removed permanently from Microsoft's site.