We're moving more and more of our systems from .Net Framework 4.8 to .Net 6 and are starting to get concerned about when Laserfiche will offer a version of the SDK compatible with .Net so it won't interfere with our plans. Can you give an updated answer on where this is on the Laserfiche roadmap?
Question
Question
Replies
Hi David,
We're interested in hearing more about the specific way(s) that the Laserfiche SDK's .NET Framework 4.8 libraries would interfere with your overall .NET 6 plans.
Per Microsoft's .NET Framework Support Policy:
.NET Framework 4.8 is the latest version of .NET Framework and will continue to be distributed with future releases of Windows. As long as it is installed on a supported version of Windows, .NET Framework 4.8 will continue to also be supported.
Do you have custom .NET Framework applications with custom Laserfiche SDK integrations that you're migrating to .NET 6 or something similar?
To the best of my knowledge, releasing a .NET 6 version of the Laserfiche SDK .NET libraries is not on the current roadmap. We do provide libraries for the Web API on Laserfiche Cloud that target .NET 6 and .NET Standard 2.0, though I realize that is not currently helpful for your self-hosted system.
We have a custom asp.net application currently on .Net Framework 4.8 that uses the existing SDK to create documents and add pages. We also use the existing COM OCR tool. We're still in the early stages of migrating to .Net 6 and are wondering how we're going to handle our Laserfiche integration. We currently run our app on a VM in Azure, but have been migrating to Azure App Services
Gotcha. With regards to page generation, I'd strongly recommend switching to using Laserfiche Distributed Computing Cluster (DCC) for page generation if/when you update that integration for the reasons described here.
I emailed you some info about .NET 6 I can't post on Answers yet.
Any updates about .net 6 that are shareable?
The crux of it is that we recommend using the new self-hosted API Server (which itself is built on .NET 6) for new or migrated integrations.
Understood. Thanks for the answer.