In windows, ms-office has the functionality of Installed Addins, wherein people can extend functionality of office. is there any such framwork for addins in Mac?
I have searched at many places, and ans i have found is no. the only way is by injection and swizzling. but I want some stable way to do it. I want to use office API's.
You can use office addins
https://dev.office.com/docs/add-ins/overview/office-add-ins
This will work on Mac also
The best way to achieve this to use Office Web-Addins for development. This works for all the scenarios: Office Web, iOS, Android, Windows and Mac as you can install it from the Microsoft Store.
Related
I am looking for the way to implement MS Word plug-in for Mac and Windows. The plug-in should work with all versions of Microsoft Office (Microsoft Office 2003, Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, Microsoft Office 2016) and should work on Windows XP - Windows 10. It should work on MS Word on Mac also (at least on the latest versions).
It seems to be impossible to create one app for all of this OS and versions.
Description of the plug-in: The plug-in should help user to find the definition of any word (the definition will be in the beginning of this file or in the other file on the user's local disk). For example, user place mouse over word "math", a plug-in shows pop-up with definition "Mathematics (from Greek μάθημα máthēma, “knowledge, study, learning”) is the study of topics such as quantity (numbers), structure, space and change".
I am thinking about some variants of implementation.
First variant. I can make plug-in with help of WinForms and Microsoft.Office.Interopt for all Windows OS and versions of MS Office. I can create add-ins for Word on Mac with help of JavaScript. (Add-ins on JavaScript don't work on Microsoft Office versions < 2013).
Second variant. I can create plug-in with help of VBA for both platform and for all versions.
Are these variants possible? What the best way to create plug-in for Windows and Mac?
First variant. I can make plug-in with help of WinForms and Microsoft.Office ...
This, sound to me, way you should go if you would like to support older Office products (2010 and older). You would create VBA or COM/VSTO version for older versions on Windows. For older versions of Mac (ex:Entourage) you should consider AppleScript scripting extendability. Office Add-in (JS API) for newer versions on Windows and Mac together.
Second variant. I can create plug-in with help of VBA for both platform and for all versions.
No such thing as VBA add-on for Mac. You may efficiently use AppleScript for scripting certain actions in older Office for Mac.
This is all about your requirements. At the end you will make your decision. I would go with Office JS API as the start and later on see if you have strong demand of your app for older versions of Office.
Yes it is possible, but refine your requirement.
Go for Apps for Office (Windows + Mac) and not Com Add-ins (Only in Windows).
I'm running Ubuntu 17.04 and learning VB. I cannot find any extensions for VB.NET.
Is there an extension or would a Windows VM be a better option?
I couldn't find anything on the Marketplace other than VBScript and VBA extensions:
VS Marketplace: VB.NET extensions
But since you are learning VB.NET I would suggest to download Visual Studio Community and play with it and develop an application. Then you're also learning the .NET environment.
I started the same with Forms applications, but now only use WPF, because it's a better option to design nicer GUIs.
If you really want to use VS Code then an VM or dual boot is your best bet.
I have a few add-ins for Excel and Word 2007-2016. And I don't understand a few things. My project use some dlls, like Microsoft.Office.Tools.Common, Office.dll, some excel, word and common interop's. And these files can be found in a few places at the same time, different versions of them (like program files, windows/assembly, windows/Microsoft.Net/assembly). So I don't know which version to use. And also, if user has VSTO installed, I suppose he has these files. So why do I need to provide them? What do we install exactly when we install VSTO? Which part is for what and which installation place is from which component? I think I don't do it right, because I found out that Excel loads two different versions of the same file at the same time.
Those are a lot of questions, and many of them depend very much on exactly what you provide with your solution...
The case of the PIAs ("Office dlls") is relatively clear cut:
You do NOT need to (and should not) distribute the Office PIAs with a VSTO solution, with the possible exceptions of 2007 and 2010. In these versions, installing .NET support was optional and not default. That's why there are redistributables for these versions, and not for others. Your installer needs to check whether they're present (same as with the VSTO runtime and the version of the .NET Framework) and install only when necessary.
Office always installs the PIAs into the GAC and your solution will find them there. It makes no difference where you referenced them on your developer machine.
The PIAs in the GAC are only available via the COM tab in the Visual Studio dialog box for inserting references. Many .NET developers didn't find them there, so Microsoft delivers a (ONE) single set of PIAs with VSTO and copies them to a Visual Studio folder so that they'll show up in the .NET tab of the dialog box. The only problem with this is that you get only the set of PIAs for the version of Office that was "current" when that version of Visual Studio was released, meaning you may get the impression you can't develop against any other version because you don't find the PIAs in the .NET tab (but they will be in the COM tab).
Rule of thumb: Always, always develop your code using the earliest version of Office you plan to support. There are two reasons for this: 1) You can only use functionality that will be available to all versions of the Office application (Office is generally backwards compatible); 2) Office is designed to migrate references to older sets of PIAs to newer sets, but not the other way around.
There's a good article on deployment pinned at the top of the VSTO forum on MSDN that "sorts" a lot of requirements for various versions of VSTO and Office: https://social.msdn.microsoft.com/Forums/vstudio/en-US/1666d2b0-a4d0-41e8-ad86-5eab3542de1e/deploying-office-solutions-to-end-user-computers?forum=vsto for add-ins targeting 2007-2010. For later versions, see the MSDN documentation: https://msdn.microsoft.com/en-us/library/bb386179.aspx
I have created a simple plugin and installed it on my outlook (for windows). It works fine. However i want to know - can I install the same plugin on outlook (for Mac)? If so, Please guide. Thanks!!
No, you can't. Office/Outlook for Mac doesn't support add-ins. The COM technology (on which Office add-ins are based) is for Windows only.
The only possible option is to develop a VBA macro instead.
Given that the iOS emulator only runs on OS X, what are reasons that people do MonoTouch development on Windows? They offer MonoDevelop for both Windows and OS X.
Some people prefer Visual Studio. Some teams may have invested in tools (like ReSharper, etc) that run in Visual Studio. And teams that maintain other .NET projects may not to switch to Macs as their primary environment.
The idea of only being able to place an app using ONLY the mac tools is not ENTIRELY correct. You are completely able to use the iTunes connect website https://itunesconnect.apple.com/WebObjects/iTunesConnect.woa/wo/4.0.0.7.3.0.9.3.1.1 to place apps on the app store, and you only need the xcode tool for stuff like using the simulator and other options such as that. The reason why people do things such as program on a Windows is because some people are more native with the way the UI works on Windows than on a Mac, as they are quite different. The Windows is more visual, and it offers a simple way to get to things; although the Mac is more user friendly when it comes to the way applications are handled in the core of them. Also, people don't always want to pay the 1200+ price for a Mac machine, when yet they can spend 200+ on a simple Windows OS machine, and still possess the same kind of options. Another thing, you can always run Windows through a mac, so it's kind of a positive negative situation in almost any circumstance.
Hope this helps!
My personal reasons for using Visual Studio currently for my iOS development are:
I'm doing mixed-client-and-server development, and have a single solution with several project types which Xamarin Studio doesn't yet support - or which it only partially supports:
Portable Class Libraries
Azure website projects
WindowsPhone projects
WindowsStore projects
Resharper and the Visual Studio productivity tools and are key parts of my toolchain - they really do make me more productive. (There are other tools too which I'm more familiar with on the PC - e.g. even things like notepad++ and Paint.Net)
Because of my last 20 years on Windows I'm faster at working on the PC - although I am getting quicker at using the Mac.