Skip to content

Conversation

hayer
Copy link

@hayer hayer commented Oct 25, 2019

This is an attempt at support .NETStandard 2.1.

I know the code at the moment isn't looking very nice. This was just a spike to check while converting our main project to .NET Core 3 and I needed DocX.

Next steps;

  • Check that versioning with the assembly info is correct
  • Generate separate keys for the *.NETCore projects?
  • Consider how WindowsIdentity.GetCurrent().Name is used originally

@XceedBoucherS
Copy link
Collaborator

Hi,
If you are looking for .NET Standard 2.0 support of DocX, you can try it for free for 45 days here : https://xceed.com/xceed-words-for-net/ under the name "Xceed Words for .NET".

This is the commercial version of DocX.
v1.6 supports .NET Standard 2.0.
Thank you.

@hayer
Copy link
Author

hayer commented Oct 28, 2019

So there is no plan for supporting this in the free part? Am I allowed to implement .NET Standard support myself?

@XceedBoucherS
Copy link
Collaborator

Hi,
For now, the .NET Standard is only part of the Commercial version of DocX. But it could change in the future. You can try to implement it yourself, but the official versions supporting .NET Standard is "Xceed Words for .NET" v1.6 and up.
Thank you.

@patrickklaeren
Copy link

Hi, For now, the .NET Standard is only part of the Commercial version of DocX. But it could change in the future. You can try to implement it yourself, but the official versions supporting .NET Standard is "Xceed Words for .NET" v1.6 and up. Thank you.

Must say Xceed is doing the community more and more disservice here.

You've already made clear this is for community consumption only, i.e. no commercial support. Why not merge a person's large effort to get this to .NET Standard?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants