.NET Core 3.1
Idea shared by Transpera Technologies Inc. - 4/11/2020 at 9:39 PM
Planned
We use FileUltimate for file managers on the back-end of many corporate websites, and we've moved our standard offering over to .net core 3.1 for many reasons.  Unfortunately FileUltimate is the one piece of the puzzle that we can't get working in our new apps.

We can use it in a .net core 3.1 app if the target server has the 2+ assemblies installed, but when deploying to a containerized service that targets a single version of the .net core sdk it fails to load the dependencies for GleamTech.

Is .net core 3.1 on the horizon? Previous versions of .net core seem to be getting left in the rearview mirror very quickly by MS and the community at large.

2 Replies

Reply to Thread
0
Cem Alacayir Replied
Employee Post
At the time, we added .NET Core 3.0 compatibility (November 14, 2019), .NET Core 3.1 was still in preview so we didn't check it but now it's retail so we will check it. They usually break a few things (like in 2.1, 2.2 and 3.0) in new versions, usually for security purpose. I will let you know soon.
0
Cem Alacayir Replied
Employee Post
Looking at https://docs.microsoft.com/en-us/dotnet/core/compatibility/3.0-3.1 , there doesn't seem to be a breaking change for ASP.NET except cookies, so it should work with 3.1.

> but when deploying to a containerized service that targets a single version of the .net core sdk it fails to load the dependencies for GleamTech.

What exact error do you get?

Reply to Thread