I have a .net application that intercepts heavily (today with excel, tommorrow with the entire office suite) with the office, and I am very worried that in 2013 there was only CTR (except for volume licenses).
I have been following the Google sync fiasco since 2013 and keep reading. A whole restructuring is required to support the installation of CTR, but I am “very ready” to do it, I can’t find any information about this, does anyone know how to actually interact with CTR office 2010/2013?
I'm not looking for ways to get a version without CTR, I want to program in such a way that I can support both of them and not push the burden on my clients to switch the version (which they won’t do anyway). I also do not program add ins (located inside the application), but external .net applications that should be able to interact with the office suite, as I always did with excel interop (the ability to extract an executable instance and process them or start new instances and access to everything that the interaction interface provides).
So, since I am ready to restart my project from scratch, but CANNOT impose on my clients a specific office installation (both media and non-standard parameters), what is the appropriate way to interact with CTR Office 2013? Will this suitable way work with versions without CTR, or do I need two code paths? Any help is appreciated, because if I cannot find a solution to this, my program is no worse than dead.
source share