Question

Updating .NET and .NET Core

Laserfiche

Updated one day ago

asked on January 23

One of our Clients currently has .NET (6.0) installed on their servers. This version is no longer supported and has reached its end of life.

They are planning to update to the recommended version of 9.0. Since it’s a few versions jump, they are asking if this would have any impact on their current Laserfiche System and in the future?

https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

0 0

Answer

SELECTED ANSWER

replied on January 23

Self-hosted Laserfiche products, except for the Laserfiche API and early versions of Audit Trail 11, only use .Net Framework, not .Net Core.

For Audit Trail 11, please make sure you are running the version mentioned in KB 1014554.

The Laserfiche API Server does require .Net 6 and cannot be upgraded. We are planning a release for later this year to update it to a newer version of .Net.

I would recommend that you and your customer evaluate the resources you want to spend on keeping .Net up-to-date when picking a version. Version 9 is going out of support before version 8 because only even versions get long term support.

1 0

View 1 previous reply

replied on January 30

Hi Miruna - Do you have any visibility on when the Audit Trail will no longer require ASP.Net 4.8?

0 0

replied on January 31

We have no plan to remove the dependency on .Net Framework 4.8 (and its ASP.Net component) from our web products.

Why is requiring ASP.Net a problem?

0 0

replied on January 31

Thanks Miruna - It's not an issue, I was confusing it one of the many other flavors and variations of .Net.

0 0

Replies

replied two days ago

Hey @████████! Recently started working with the Laserfiche Repository API and ran into this issue. We no longer allow dotnet 6 to run internally but I may be able to get an exception granted. Do you know if there's a timeline for the release to support more modern dotnet versions?

Thanks!

0 0

replied one day ago

Following up on my reply from yesterday. We were able to find what may be a workaround for this. The *runtimeconfig.json file located in the install directory can be modified to force dotnet 8. We tried this and are at least able to connect to the site without a dotnet error. Unsure if we will run into issues while sending calls but wanted to share in case anyone else comes across this post.

Question

Question

Updating .NET and .NET Core

Answer

Replies

Sign in to reply to this post.