Since Lync is the replacement to Microsoft Office Communicator, does that mean that if I write an app that integrates Microsoft Office Communicator 2007 R2, and then later I upgrade to Lync 2010, will I have to rewrite the integration portions of my app?
Presumably you're talking about client side integration with OCAA or UCCA? These are both still supported against Lync 2010, so your app should still work if you upgrade. However, one or both of these APIs will definitely not be supported against the next version of Lync.
Related
I need to develop a windows app program. I have Office 2013 in my Machine. And I need to develop the app which supports Office 2013 User machine also. How to do reference dll for it?
I expect that I will develop using Office 2013 and it should supports(the app should work) on Office 2010 also
I have made the app with excel 14.0 reference file. So that if a machine have excel 2010, then the app couldn't open on that
Things go the other way around with Office!
To support all versions of Office back to 2010, you have to develop and maintain your WinForms application with Office 2010, that is the oldest version of Office that you want to support. Whenever you deploy your application on a machine that has Office 2010 or a more recent version, it will work. But it will fail with older versions such as 2007 and 2003.
This design makes sense since one cannot expect that a workook developed with say, Excel 2016, can be run by Excel 2010 without error. The 2016 workbook may use features that did not exist in 2010.
I have developed an addin for MS Office Word using 2010 project template (VSTO C#)
It is working in Windows Office Word. Now I need to install it in Mac OS ? Is it possible ?
Do you have any link ?
The VSTO technology is not supported on Mac OS.
If you need an add-in that runs on both platforms, then you need to use the Office JavaScript "web add-in" functionality (which also works in the on-line versions of Office and on iPad, by the way).
This is a good place to start in the official documentation: https://learn.microsoft.com/en-us/office/dev/add-ins/overview/office-add-ins
For support, use the office-js tag here on Stack Overflow.
I'm new to UCMA and I'm trying to set up an environment to build UCMA applications.
I have 2 Windows 2008 Servers, one for Active Directory DC and an other for Lync 2013 Server, can I use either of these machines to also run/develop my UCMA applications by installing VS and UCMA 4.0 SDK ?
Or will I need a separate Windows 2008 server ?
You can use your Lync Server as the App server, I can't find proof but I'm pretty sure that Microsoft advise against this and although I suspect it is fine in a lab environment you could come across undocumented issues.
Hi We have a web based SharePoint 2010 webapp and our client is upgrading their os with Office 2013. Would there be any compatibility issues when uploading and downloading document from Document library of our SharePoint app.
Do you guys foresee any concerns of any compatibility issues. Probably any new formats with aren't available with SharePoint 2010.
I can't imagine there being any problems, Office2013 does not use a different file format, it's just a new interface.
There are some new integration features between Office2013 and SharePoint2013 which your client will not have access to in SharePoint 2010, but they certainly won't impact on the functionality of your existing SharePoint Apps, and I can't imagine anyone even noticing that they don't have access to a new feature that they never had before!
I'm facing one issue, actually I need to create one application in C# using VS2012, .Net framework 4.5 which reads excel and do some operation, but the issue is target machine doesn't have MS Office client installed on it.
And one restriction is I can't use the other open assemblies like Open XML etc. I have to only use the 2010 PIA.
It'll be great if someone can explain me how can implement this?
This can not be possible without installing MS Office on server. To use PIA you have to install the MS Office on server. Otherwise, if you doesn't want to install MS Office on server, it's better to use Open XML.