Docx not working .Net core projects

Question

Docx not working .Net core projects

Opened this issue 6 years ago · 32 comments

Tried using Docx in .Net core 2 projects like console / Azure functions. Getting below issue

Could not load file or assembly 'System.IO.Packaging, Version=0.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Answer 1 · 2018-05-27T21:13:30.000Z

I am having the same issue.

I saw another project, OpenXML in which another was complaining about the same issue. Their response was you need a signed certificate to use their project. I am wondering if this one requires the same now.

OfficeDev/Open-Xml-PowerTools#121

Answer 2 · 2018-06-01T19:28:18.000Z

Hi,
DocX is currently not working on .Net Core.
This is a feature we are working on.
Thank you.

Answer 3 · 2018-06-02T22:10:56.000Z

Thank you for the response. Any ETA on when this will be completed?

Answer 4 · 2018-06-04T12:15:23.000Z

Hi,
No. We are going by priority.
This is something important we want to achieve, but no released date has been fixed for now.
Thank you for your patience.

Answer 5 · 2018-06-06T08:08:03.000Z

Hi, tried to add System.IO.Packaging form NuGet - this package helped, no errors - the document was successfully created, but zero content inside.

Answer 6 · 2018-07-06T12:08:42.000Z

I also worked around the issue by adding System.IO.Packaging manually, with NuGet, but ran into the same problem with zero content. I'm guessing whatever API the DocX lib uses to write to Word files isn't conformant with .NET Standard.

Answer 7 · 2018-07-10T14:28:45.000Z

Hi,
yes we are aware of this (zero content).
The priority is this issue is high now.
You should get a response on this in the following weeks/months.
Thank you for your patience.

Answer 8 · 2018-07-10T14:36:38.000Z

Will this get into community edition?

Answer 9 · 2018-07-10T16:16:41.000Z

No decision has been made related to this at this point. We will keep you up to date.
Thank you.

Answer 10 · 2018-07-26T08:00:59.000Z

There is a fork that works with netstandard 2.0, https://github.com/wtulloch/DocX. I suppose you could look into how he solved it.

Answer 11 · 2018-07-26T08:09:18.000Z

Well there is this comment: This is a port of the original DocX that has been updated to target .NET Standard 2.0. To limit any changes to the original code base this will currently only work for on Windows OS due to an existing dependency on Windows.Identity. which is a bit killer because the main reason people want NET Standard is for DocX to work on linux right?

Answer 12 · 2018-07-26T15:43:32.000Z

I agree that it is far from ideal. In my case it would work, but a general solution is always better.

Answer 13 · 2018-07-26T15:48:16.000Z

If you have Windows I assume you have NET 4.5? So Why would it work for you in case of wtulloch version and it wouldn't on Xceeds ?

Answer 14 · 2018-07-29T20:09:38.000Z

I have not looked into the difference between the packages. In short I get the same message as @snober. When I add System.IO.Packaging through NuGet or add a reference to the assembly I get the zero content issue.

Answer 15 · 2018-07-29T20:29:48.000Z

You're saying this works on Azure/Console and solves snober's problem?

Answer 16 · 2018-08-13T14:57:19.000Z

See also: #31

Answer 17 · 2018-10-05T18:53:44.000Z

Hope this influences priority a bit but we have a bunch of people that want to move to PowerShell Core (and use this with that) but can't because of this issue.

Looking forward to this 😊

Answer 18 · 2018-11-05T21:07:34.000Z

This feature will be available in the next release of "Xceed Words for .NET" : v1.6.
Thank you.

Answer 19 · 2018-11-22T03:06:33.000Z

Any ETA for that?

Answer 20 · 2018-11-22T06:40:38.000Z

From other threads begining 1st quarter of 2019. Also keep in mind this will be only in pay version. No core support for free one.

Answer 21 · 2018-11-22T16:05:03.000Z

That is very sad. I cannot justify spending that kind of money just for my own little personal project

Answer 22 · 2019-01-31T01:49:41.000Z

Looks like this just shipped https://xceed.com/release-notes/#words-net-1.6.19076.19550

Answer 23 · 2019-02-06T00:48:32.000Z

@tcreek https://github.com/OfficeDev/Open-XML-SDK

Answer 24 · 2019-02-06T19:09:14.000Z

Thanks for that link @vovikdrg . That is very very helpful. Now I can complete my person project without having to fork out a lot of money to do it, or do the deep development of just wanting to manipulate a document

There was an article just about this very issue in the January 2019 edition of Linux Journal. "Some Thoughts on Open Core. Why open core software is bad for the FOSS movement."

Answer 25 · 2019-05-04T13:57:24.000Z

Very sad that until now there is no support for .NET Standard.

Answer 26 · 2019-05-05T03:39:51.000Z

Especially since .NET is now available on Linux

Answer 27 · 2019-10-23T20:22:44.000Z

Apparently this still isn't fixed for the free version (DocX) in the latest stable, 1.4.1.

Answer 28 · 2019-10-23T20:24:29.000Z

Correct, as they state it would not be available for the free version any longer. Alternatives have been posted in previous messages.

Answer 29 · 2021-10-06T12:58:15.000Z

Still no fix in 1.8.0 :(

Answer 30 · 2021-10-06T13:03:38.000Z

Still no fix in 1.8.0 :(

I have moved on to https://github.com/OfficeDev/Open-XML-SDK as @vovikdrg pointed out. It works out just fine.

Answer 31 · 2021-10-06T13:25:32.000Z

Still no fix in 1.8.0 :(

I have moved on to https://github.com/OfficeDev/Open-XML-SDK as @vovikdrg pointed out. It works out just fine.

Awesome thanks. Checking it out now

Answer 32 · 2021-10-12T17:21:59.000Z

Hi,
"Xceed words for .NET" support .NET standard since v1.6 (Released on January 30, 2019).
"Xceed words for .NET" support .NET5 since v2.0 (Released on July 19, 2021).
You can try those here : https://xceed.com/en/our-products/product/words-for-net
The community edition od DocX do not support those versions for now.
Thank you.