A bit of foreword: this project, while technically doing homework, is completely under my control of 5 people. We came up with the project, determined the scope and carried out full creative control. So this is not traditional homework, it is equivalent to an older project.
One of the outputs of the system I'm developing should be very similar to a well-formatted Excel spreadsheet. We could create (or find) a graphics library and handle printing in our own code ... but in the end, we think the Excel spreadsheet file will be more portable. Since the user can open it in Excel, edit it, send by email, etc.
Access to Excel programmatically seems fairly simple (for example: http://support.microsoft.com/kb/302094 )
But my question is: what happens when Office 2013 comes out and the user uninstalls Office 2010 and installs 2013?
I will not support this project ... and I would not want anyone to open my code to reference Excel 13.0 COM.
I will use incredibly simple API functions. While I can read and write in a series of cells, as well as adjust the color of the internal cells, my code will work.
In general, how can I make VB.Net code available, which Microsoft Excel API is available on the target system? (Including future Excel APIs.)
source
share