Regarding VSTO

Mar 25, 2013 at 11:41 PM
Dear Team,

May I have a quick question, what is the relationship between this project and the VSTO (especially those DLLs in the library)?

I noticed this project does not reference to any VSTO dlls and the code was very down to metal, (which is great), is there any design purpose of not using VSTO dlls?

Best regards,

Mar 26, 2013 at 8:51 AM
To keep compatibility with cross platform, I think that is the major design decision.
Mar 26, 2013 at 11:01 AM
Thanks for reply so quick. By Cross Platform, you mean Mono, is there any reason one can not run VSTO dlls on Mono (coding issues or legal issues)?

Best regards,

Mar 26, 2013 at 11:28 AM
I do mean Mono as well as Phone and even Micro Framework. However, I don't have any knowledge of VSTO dependencies, legal or otherwise.
Mar 26, 2013 at 12:24 PM
The major reason I think is that VSTO requires you to install office, and has a much more complicated deployment scenario. Also, I believe this library may be quicker (though I haven't tested it).
Apr 9, 2013 at 3:53 PM
In comparison, VSTO is much slower. This is by far the fastest reader i've seen, the OpenXml method is good for latest excel 2007+ but the BinaryReader is smokin fast but it only works on 97-2003 excel files. VSTO is really good for direct integration with Excel itself as an application not the right choice for simply reading an excel file etc...
Apr 9, 2013 at 8:18 PM
Edited Apr 9, 2013 at 8:18 PM