I wondered about this as well.
I've managed to successfully perform the following:
I've managed to successfully perform the following:
- Download the NPOI source, rebuild the 'AllnOne' folder solution to a DLL targetting .NET framework 4.5
- Reference this DLL from a PCL
-
Use that PCL from a Windows Runtime Component for basic spreadsheet creation
- Fork this and copy the code into a PCL
-
Add in neccessary changes/conditional compilation stuff to allow building as a PCL
-
There are 3 main build errors:
a) Use of serializable attribute (I believe this can be substituted for DataContract in a PCL)
b) Use of non PCL types, namely ArrayList and Hashtable, these I think can be swapped for List and Dictionary, but it could take some time to swap all the references
c) Lots of references to System.Drawing stuff. I think the only way to handle this would be to extract this drawing code out of the PCL and reference it as a seperate non PCL library. unsure whether this would break the core functionality as I don't know the code too well. Will investigate in the coming weeks.