I have a couple of Excel Add ins. If I move to Office 365, will these add ins be available ? Is there any development support(VSTO) for Office 365 ?
I to have been curious about the answer to this, so went looking online. From the following site, I'd say the answer is no. It looks like developing for Office 365 is more along the lines of SharePoint development.
http://blogs.msdn.com/b/donovanf/archive/2011/06/29/office-365-developer-guidance-and-resources.aspx
I have seen advertisements online for products such as this... http://www.ocxt.com/products that look like they could provide a possible solution for taking a vsto application to the web.
I think things have moved on substantially since this question was asked. Microsoft seem to be fully committed to the Add-in approach with Office 2013 and the equivalent VSTO tooling available in VS2012.
The Office Dev Center home page has Office 2013 and VSTO Add-ins written all over it.
This MSDN Blog Post also clearly shows Add-ins are still part of the strategy.
Until the full capabilities of Desktop MS Office are available in a browser, I can't see this situation changing.
If you mean Office 365 installed on client PC then there is no issue with VSTO Add-ins. Our Chem4Word Add-in is using Office 2010 VSTO and happily works with 2010, 2013, 2016, 2019, O365.
If you mean Office 365 on-line then you have to redesign them using the Office 365 Javascript API
Related
One of my add-ins, Formula Formatter, works well in Office 365. However, one client told me it cannot be loaded in Office Professional Plus 2016.
Does anyone know what may be the reason? Should we do something special in the manifest xml for Office Professional Plus 2016?
In its manifest, Formula Formatter specifies the requirement set ExcelAPI with a minimum version of 1.2. Per the documentation for that requirement set (https://dev.office.com/reference/add-ins/requirement-sets/excel-api-requirement-sets) your customer will need to be running "Version 1601 (Build 6741.2088) or later". Customers that have a non-subscription version of Office won't have that requirement set.
If you remove the requirement set from the manifest, your add-in would be available on Office 2016 but you would need to ensure that your add-in has a good user experience when they are not present.
All the questions/answers I have seen so far are old and do not provide a definitive answer.
Also what can I use locally and what can I use online?
what can I use locally and what can I use online?
You may use your VSTO and VBA add-ins for Office Desktop application on Windows.
Office applications on Web (online) has extensibility via Office.js API. Microsoft current name is "Office Add-ins", you may try them by loading into your Office application (excel) from Office Store. If you want to develop add-in based on this technology I would suggest to start over here: Office Add-ins platform overview. The conception behind of this technology is "build once, use everywhere where Office runs". That means your add-in may work for Office Desktop on Windows, Office Desktop on Mac, Online versions as well as some mobile platforms (subject to availability)
Office 2016 has been released, where can I get the list of the control IDs?
Searching the microsoft.com site I can only find office 2007-2013 control identifiers.
Microsoft has published the help files for Office 2016. You can get it from:
https://www.microsoft.com/en-us/download/details.aspx?id=50745
They were not published yet. Try to use for Office 2013 or wait until Microsoft publishes the full list of controls for Office 2016.
UPDATE: The list of Office 2016 ribbon control IDs is available for download.
As there is a drastic change in architecture from SharePoint 2010 to 2013, I would like to know what are the restrictions for a developer while developing Solutions/Apps for Office 365.
In SharePoint 2010, only sandbox solutions were allowed on Office 365, but in SharePoint 2013 the sandbox solutions are depreciated and App model is introduced. Would be glad if someone can throw some light on what is allowed and what is restricted on Office 365 in the new 2013 environment.
Sharepoint 2013 is a game changer, starting with the fact now is possible to use framework 4.5 and, since the new release of visual studio 2013, it's possible to use MVC. From a developing point of view you have to know there are two flavors:
Sharepoint hosted. In this case, your whole application is installed within the Microsoft servers. Because of this, you MUST use client object model and javascript. No server code at all. So you will configure your sites, libraries, lists, etc with 365 and then access this information using the Sharepoint javascripts libraries. If you are familiar with js ans sp js the you won't have any problem.
Autohosted. In this case you can choose between azure or your hosting (provider hosted) in both cases you can use a more traditional aproach, with your server code, classes, aspx and so on. The difference is when you deploy your application, in this case the app is installed just as a reference in 365 and all the code in your hosting provider. In fact all your application will be displayed in 365 within an iframe. Keep in mind you will be dealing with lots of cross domain scripting.
Last but not least, you have one final flavor, but it's not 365, Sharepoin onpremise, in this case this is your own sharepoint, you create, manager, develop or deploy whatever you want. This is very similar to the current sp2010 model, so, I guess you already now what you can do.
For more information:
http://msdn.microsoft.com/en-us/library/office/apps/fp179930.aspx
http://blogs.msdn.com/b/amigan/archive/2012/12/10/part-2-introduction-to-sharepoint-2013-app-model.aspx
I have a site developed in Microsoft Office SharePoint server 2007 and I have installed Microsoft office 2010 on my machine. When I try to access excel file stored in document library. It gives me an error saying that it requires a Windows SharePoint Services compatible application.
It was working fine when I have Microsoft office 2007. So I am confused whether SharePoint is compatible with office 2010 or not...?
Thanks
Sachin
Yes it is compatible and it should work. A number of things could be going on.
The OWSSUPP.DLL may not be registered correctly.
You could register it manually or reinstall
If you have the 64 bit version of office there are some known issues opening data in SharePoint.
http://www.knowsharepoint.com/2010/06/sharepoint-datasheet-view-and-office.html
Windows SharePoint Services Support files may not be installed.
in this case install these through Add/Remove programs. It's in the office tools section of the MS Office application.
If you have some applications that were part of Office 2003 or earlier you may need to uninstall them.