A few months ago, I put together a simple conceptual piece of software for a small company with an idea for a document editing tool. It is clear that the company wanted this tool to be integrated into Microsoft Word in order to maximize its availability for the average user.
I essentially wrote a base library with all the basic functions as a C # project, and then used VSTO to run it inside Word. In fact, it was like a tape solution; but then I had (practically) zero experience in developing tools for integration with MS Office, and this was just a proof of concept in any case.
Well, the company was very pleased with my work as a whole, and they want to move from a "proof of concept" to a real deal. Fortunately, as I said, the basic functionality is there, and they will only need to be tweaked and improved. My main problem is how to build an application that will be integrated with MS Word in a clean and polished form and which can be easily deployed in accordance with the usual expectations of users (i.e. just run the installer and voila, there in Word) .
It seems that I remember something that no one uses VSTO for real professional projects. It's true? Lying? What are the alternatives? And what are the tips and errors that I should know about before embarking on this issue of integration with MS Word?
source
share