Support for NET Core 3.0 and .NET Standard Version 2.1

Idea shared by Robert Madrian - 9/24/2019 at 12:23 AM

Completed

Hello, please create a native version of DocumentUltimate for NET Core 3.0 with .NET Standard Version 2.x

because ASP.NET Core 3 is not running on .NET Framework 4.x

robert

9 Replies

Reply to Thread

Cem Alacayir Replied

11/1/2019 at 3:15 AM

Employee Post

FYI, this is now supported.

Version 5.0.0 - October 31, 2019

Added: .NET Standard 2.0 DLL/nuget target is now available. This DLL can be used with ASP.NET Core 2.0+ web applicationsand .NET Core 2.0+ console/desktop applications. This means you can now use it with "ASP.NET Core on .NET Core" projects inaddition to "ASP.NET Core on .NET Framework" which was already supported.Note that with this initial release, document format support on .NET Core is limited, however we plan to port remaining formatsrapidly from .NET Framework version. Please see below link for a complete list of currently supported formats on .NET Corehttps://docs.gleamtech.com/documentultimate/html/supported-formats-netcore.htm

Robert Madrian Replied

11/1/2019 at 4:39 AM

Hi Cem,

Very good news - but we have to wait till support for Email Formats are available (*.msg)

robert

Cem Alacayir Replied

11/12/2019 at 8:33 PM

Employee Post

FYI, almost all formats (except Cad formats) are now available:

Version 5.1.0 - November 13, 2019

Added: Almost all formats are now ported to NET Standard 2.0 DLL/nuget target. Only remaning formats are Cad formats whichwill be ported soon. Please see below link for a complete list of currently supported formats on .NET Core:https://docs.gleamtech.com/documentultimate/html/supported-formats-netcore.htm
Fixed: "Object reference not set to an instance of an object" error at app.UseGleamTech() line with ASP.NET Core 2.1 and 2.2 projects.Now ASP.NET Core 2.1 and 2.2 compatiblity is ensured.
Fixed: Fonts of the document were not being loaded on IE and Edge so the document did not look like the original (probably since 4.8.0).
Fixed: Unnecessary error when one of the client events Printing and PrintProgress, were set and the other one wasset to empty string.

Note that currently there seems to be a problem with ASP.NET Core 3.0 compatibility (you may see a blank page with HTTP 500 error for CSS files when you run). This will be fixed in next release. However it should work good in ASP.NET Core 2.0, 2.1 and 2.2.