My main development computer has now been updated to Office 2010 (it used to have Office 2003 installed). I gave the ESI test suite a quick run to see what would happen. The results aren't that bad. I was concerned that the 2003 Interop assemblies would not work with Office 2010, but in the main it seemed to work (one thing Microsoft are good at is supporting old API interfaces).
The findings so far are:
1. There is an extra semi-colon in some of the exception messages. From the user's perspective this is cosmetic. However the test suite tests for the exact expected message so it is listed as a failure. We should fix this
2. More annoyingly when saving certain files (almost certainly the 2003 version files) a pop-up is displayed warning about unsupported features. This will annoy the user and makes running the automated test suite a manual process. We need to find a way of suppressing this
Graham
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My main development computer has now been updated to Office 2010 (it used to have Office 2003 installed). I gave the ESI test suite a quick run to see what would happen. The results aren't that bad. I was concerned that the 2003 Interop assemblies would not work with Office 2010, but in the main it seemed to work (one thing Microsoft are good at is supporting old API interfaces).
The findings so far are:
1. There is an extra semi-colon in some of the exception messages. From the user's perspective this is cosmetic. However the test suite tests for the exact expected message so it is listed as a failure. We should fix this
2. More annoyingly when saving certain files (almost certainly the 2003 version files) a pop-up is displayed warning about unsupported features. This will annoy the user and makes running the automated test suite a manual process. We need to find a way of suppressing this
Graham