Oracle.ManagedDataAccess.Core support for ASP.NET 5

user5548540

Just created new ASP.NET Core project with .NET 5. Added NuGet package Oracle.ManagedDataAccess.Core (2.19.100). But still got BinaryFormatter exception during runtime at "connection.Open()". AddOracleTypesDeserialization at ConfigureService or direct before instantiating OracleConnection does not help here. See https://github.com/dotnet/aspnetcore/issues/27872

Alex Keh-Oracle

You have the following package reference:

    <PackageReference Include="Oracle.ManagedDataAccess.Core" Version="2.19.91" />

The 2.19.100 version should be used instead.

user5548540

I use 2.19.100, and I do not use DataTables or anything else. I got NotSupportedException: BinaryFormatter exception during connection.Open() as inner exception of "TypeInitializationException: The type initializer for 'Oracle.ManagedDataAccess.Types.TimeStamp' threw an exception." which is an inner exception of "TypeInitializationException: The type initializer for 'OracleInternal.ServiceObjects.OracleConnectionImpl' threw an exception."

I want to say, that 2.19.100 seems not to solve all problems with BinaryFormatter. But it looks like only to appear in ASP.NET.

Alex Keh-Oracle

Can you upload a simple test case? We'll try to reproduce the problem and debug.

Alex Keh-Oracle

Another customer who ran into what is likely the same issue has given us a test case. Can you enable the following to disable the binary formatter until we provide a bug fix?

<EnableUnsafeBinaryFormatterSerialization>true</EnableUnsafeBinaryFormatterSerialization>

User_DW5ZB

Hello,

This is a blocker for us to migrate to dot net 5. Do we have any updates on the progress and somewhere we can track?

We cant use that flag because it has some serious security implications, hence the reason Microsoft decommissioned it.

Thanks.

Alex Keh-Oracle

Oracle will publish a patched ODP.NET version on NuGet Gallery at the beginning of the new year.