Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
All of these projects use Microsoft's OpenXML SDK for Office behind the scenes: 1. .NET (F#, C#) The F# Guide recommends NPOI, which also seems to be the most popular and most up-to-date, but the...
Answer
#3: Post edited
by
toraritte
·
2023-11-11T22:39:46Z (about 1 year ago)
Add python tools
- All of these projects use Microsoft's [OpenXML SDK for Office](https://learn.microsoft.com/en-us/office/open-xml/open-xml-sdk) behind the scenes:
- ### 1. [.NET](https://dotnet.microsoft.com/en-us/) (F#, C#)
- The [F# Guide](https://fsharp.org/guides/data-science/#excel-interop) recommends [NPOI][1], which also seems to be the most popular and most up-to-date, but there are others as well ([ClosedXML](https://github.com/ClosedXML/ClosedXML), [EPPlus](https://github.com/EPPlusSoftware/EPPlus)).
- ### 2. Elixir
- + [`elixlsx`][2] seems to be only for manipulating existing Excel files and [its documentation](https://hexdocs.pm/elixlsx/readme.html) is very sparse.
- + [`xlsxir`][3] on the other hand appears to be the full package and [its documentation](https://hexdocs.pm/xlsxir/overview.html) is in a somewhat better shape.
- [1]: https://github.com/nissl-lab/npoi
- [2]: https://github.com/xou/elixlsx
- [3]: https://github.com/jsonkenl/xlsxir
- All of these projects use Microsoft's [OpenXML SDK for Office](https://learn.microsoft.com/en-us/office/open-xml/open-xml-sdk) behind the scenes:
- ### 1. [.NET](https://dotnet.microsoft.com/en-us/) (F#, C#)
- The [F# Guide](https://fsharp.org/guides/data-science/#excel-interop) recommends [NPOI][1], which also seems to be the most popular and most up-to-date, but there are others as well ([ClosedXML](https://github.com/ClosedXML/ClosedXML), [EPPlus](https://github.com/EPPlusSoftware/EPPlus)).
- ### 2. Elixir
- + [`elixlsx`][2] seems to be only for manipulating existing Excel files and [its documentation](https://hexdocs.pm/elixlsx/readme.html) is very sparse.
- + [`xlsxir`][3] on the other hand appears to be the full package and [its documentation](https://hexdocs.pm/xlsxir/overview.html) is in a somewhat better shape.
- ### 3. Python
- + `openpyxl`\
- There is a great guide by Real Python:[A Guide to Excel Spreadsheets in Python With `openpyxl`](https://realpython.com/openpyxl-excel-spreadsheets-python/).
- + [`xlwings`](https://www.xlwings.org/)
- > INFO\
- > Requires Excel to be installed. See `xlwings`'s [install docs](https://docs.xlwings.org/en/stable/installation.html).
- [1]: https://github.com/nissl-lab/npoi
- [2]: https://github.com/xou/elixlsx
- [3]: https://github.com/jsonkenl/xlsxir
#2: Post edited
by
toraritte
·
2023-11-10T14:35:28Z (about 1 year ago)
- All of these projects use Microsoft's [OpenXML SDK for Office](https://learn.microsoft.com/en-us/office/open-xml/open-xml-sdk) behind the scenes:
- ### 1. [.NET](https://dotnet.microsoft.com/en-us/) (F#, C#)
- The [F# Guide](https://fsharp.org/guides/data-science/#excel-interop) recommends [NPOI][1], which also seems to be the most popular and most up-to-date, but there are others as well ([ClosedXML](https://github.com/ClosedXML/ClosedXML), [EPPlus](https://github.com/EPPlusSoftware/EPPlus)).
- ### 2. Elixir
+ [**elixlsx**: An Elixir XLSX writer][2]+ [**xlsxir**: Xlsx parser for the Elixir language.][3][`elixlsx`][2] seems to be only for manipulating existing Excel files and [its documentation](https://hexdocs.pm/elixlsx/readme.html) is very sparse.[`xlsxir`][3] on the other hand seems to be the full package and [its documentation](https://hexdocs.pm/xlsxir/overview.html) is in a somewhat better shape.- [1]: https://github.com/nissl-lab/npoi
- [2]: https://github.com/xou/elixlsx
- [3]: https://github.com/jsonkenl/xlsxir
- All of these projects use Microsoft's [OpenXML SDK for Office](https://learn.microsoft.com/en-us/office/open-xml/open-xml-sdk) behind the scenes:
- ### 1. [.NET](https://dotnet.microsoft.com/en-us/) (F#, C#)
- The [F# Guide](https://fsharp.org/guides/data-science/#excel-interop) recommends [NPOI][1], which also seems to be the most popular and most up-to-date, but there are others as well ([ClosedXML](https://github.com/ClosedXML/ClosedXML), [EPPlus](https://github.com/EPPlusSoftware/EPPlus)).
- ### 2. Elixir
- + [`elixlsx`][2] seems to be only for manipulating existing Excel files and [its documentation](https://hexdocs.pm/elixlsx/readme.html) is very sparse.
- + [`xlsxir`][3] on the other hand appears to be the full package and [its documentation](https://hexdocs.pm/xlsxir/overview.html) is in a somewhat better shape.
- [1]: https://github.com/nissl-lab/npoi
- [2]: https://github.com/xou/elixlsx
- [3]: https://github.com/jsonkenl/xlsxir
#1: Initial revision
by
toraritte
·
2023-11-10T14:27:04Z (about 1 year ago)
All of these projects use Microsoft's [OpenXML SDK for Office](https://learn.microsoft.com/en-us/office/open-xml/open-xml-sdk) behind the scenes: ### 1. [.NET](https://dotnet.microsoft.com/en-us/) (F#, C#) The [F# Guide](https://fsharp.org/guides/data-science/#excel-interop) recommends [NPOI][1], which also seems to be the most popular and most up-to-date, but there are others as well ([ClosedXML](https://github.com/ClosedXML/ClosedXML), [EPPlus](https://github.com/EPPlusSoftware/EPPlus)). ### 2. Elixir + [**elixlsx**: An Elixir XLSX writer][2] + [**xlsxir**: Xlsx parser for the Elixir language.][3] [`elixlsx`][2] seems to be only for manipulating existing Excel files and [its documentation](https://hexdocs.pm/elixlsx/readme.html) is very sparse. [`xlsxir`][3] on the other hand seems to be the full package and [its documentation](https://hexdocs.pm/xlsxir/overview.html) is in a somewhat better shape. [1]: https://github.com/nissl-lab/npoi [2]: https://github.com/xou/elixlsx [3]: https://github.com/jsonkenl/xlsxir