I have all the documentation for how to develop and deploy proofing tools for MS Office on Windows using CSAPI, but how does one deploy them on Mac?
In 2010, Eric Paquin said Office 2011 for Mac would have the same API: "3rd party proofing tools companies that are relying on Windows API can now port their tools to work on the Mac"
But, I can't find any information regarding this. Anyone know where the docs for Mac development and deployment? Or if this never actually materialized?
And what about Mac Office 2016? I can find the Office Add-ins stuff, which unfortunately can't create integrated proofing tools.
(asked on Technet ages ago, but nobody there knows)
Official Microsoft documentation does exist for deploying to MS Office for Mac. If you run into this problem, keep asking your MS contact about it.
Unfortunately I can't actually share the how, 'cause NDA. But, if you have tried reverse engineering this problem, it basically is as much of a mess as you discovered.
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.
Is there a new API for developing add-ins for Office 2016 for Mac? I have seen a javascript API but I have not clear if this applies to Office for Mac 2016, Office for Windows 2013+ only or Office Web Apps only.
Please point me to an official documentation clarifying that.
Update, April 2016: MS recently made some announcements about Mac support at Build; primarily around Word & Excel. Interactive chart similar to the image below
Eventually, but not yet. The only thing that is in for Mac is Outlook Read apps.
This is an image they've shared:
My clients have bought an Office 365 SharePoint 2013 site and I'm in the process of configuring it.
Their business rules require a very complicated Workflow which can just about be developed in SharePoint Designer. However, as I'm an experienced Visual Studio .NET developer I'd rather do it programmatically and hopefully save some time.
At present I can't figure out how to connect my desktop version of Visual Studio to the Cloud-based SharePoint site. I've downloaded the Workflow Manager tool but I'm struggling to figure out how to configure the Farm Databases etc. Available documentation seems patchy.
Has anyone out there found a way of doing this? This link suggests that it might not be possible.
Thanks
Edward
According to this article it's possible, though probably not really nice.
You will have to deploy your Workflow as a SharePoint App. Which means you will only be able to call the webservices.
Another option which might be worth looking at is Nintex, which has a module for office 365 as well.
Nintex has alot of useful functions, though I don't know how good the office 365 version is.
You would have to check whether it suits your requirements.
I am writing a installer for my company's software. The specs is pretty tight: doesn't require administrator rights, good if it also include auto-update capability, have a nice UI (as opposed to the normal windows wizard UI), small and fast, robust...
I looked at Advanced Installer, which satisfy everything except having a good UI. (it shows the classic MSI installer UI which is super-duper old). We would love to have something more user-friendly.
Do you have any suggestions for installers I should look at, given these constrains?
P.S: i'm reading about Google's Omaha next, then maybe NSIS and InnoSetup / WIX...
This question is very subjective. However Office 2007, 2010, Visual Studio 2012 (aka VS11) were all developed using WiX. The software is fully open source and you can take a look at the latest weekly release for an example with a very nice UI.
Amm .. I couldn't understand if you want to develop it by yourself, or using another software, but if you do, I think that Install creator pro can be good for you.
I really want to upgrade to Visual Studio 2010. But since I do a lot of development for the Pocket PC version of Windows Mobile I cannot. (I develop for a Symbol device that does not support Windows Phone 7, so that is not a option.)
Does any one know any kind of time frame of when Microsoft plans to add support for Smart Device Projects into Visual Studio 2010?
Update: Since this is looking less and less likely without intervention from the users, Please go here and vote for this feature.
Microsoft's current public statement says that, apart from Windows Phone 7 development, there will not be Smart Device Application Development added to Visual Studio 2010.
This obviously raises concerns and has implications for a lot of people, and there are more than a few of us lobbying Microsoft very hard to change that plan and to get them to include some sort of support for Smart Device programming outside of Windows Phone.
I'm hopeful, maybe even optimistic, that their stance will change and that we will get something - even if it's only CF 3.5 targeting actual hardware (i.e. no emulator support) - at some point down the road. Right now they've got all hands on deck trying to get Windows Phone out the door, and until that happens, I wouldn't expect much for resource allocation toward other device features.
So what does that actually mean? In my mind I wouldn't postpone installing VS2010 until they have device support. My guess is it won't happen until early next year at the absolute earliest and realistically I would say mid to late next year if it happens at all. Again, I'm optimistic that it will, but I'm also a realist, so I'm not going to base my business decisions and future on it happening.
Add your support to the following Microsoft Connect Item, it's had quite a bit of interest being the 3rd highest voted suggestion so far.
http://connect.microsoft.com/VisualStudio/feedback/details/595712/no-support-for-windows-ce-and-compact-framework-development-in-vs2010
Through private conversations I've had with the Customer Advocacy Team at MS it would appear that they are really digging their heels in over this. MS reneged on promises to include Smart Device Framework support in VS2010 early on in the product life cycle.
It is really frustrating because at some point the development tools will fragment and you'll end up with having to maintain separate development, source control and build systems for targeting Windows CE. Who is to say that the tools will even work on future versions of Windows either or even if they will live side by side with future versions of VS. Remember this lack of support also hurts people doing unmanaged code on CE too.
MS is doing a great job of remaining silent here, the silence is already causing people to look at alternative platforms. Without a statement of intent no business is going to invest in Windows CE development without knowing the future of the OS and the tools to develop on it.
All recent Visual Studio versions can be installed side by side. You could upgrade now for desktop development, then when smart device support is rolled out, migrate your projects to VS2010.
http://social.msdn.microsoft.com/Forums/en/setupprerelease/thread/fce95ec7-728d-41d1-ab13-74a2fd3a4136
I am forced to have two VS installations side by side. However, another issue - that is causing me more pain is that TFS 2010 doesn't work with VS 2008 - there is a plugin, of course, but there are many issues with it which make it unusable.
So to have source control, I have installed SVN on my machine.
Microsoft once again, has proven that they have no concern for the devs at all. Their tools don't work together, backward compatibility is not there, all of which makes their dev tools a big load of crap.
MS replied to that connect issue:
Hi folks,
In the first quarter of 2013, we plan to provide tooling for Visual
Studio 2012 to create apps for Windows Embedded Compact v.Next. We’ll
be announcing more details in September, including the roadmap for
.NET CF. You can find more details this Fall in the Windows Embedded
Compact website at http://www.windowsembedded.com.
thanks, Doug Turnure Visual Studio PM