- 3,715,496 Users
- 2,242,776 Discussions
- 7,845,366 Comments
Forum Stats
Discussions
Categories
- 15 Data
- 362.2K Big Data Appliance
- 6 Data Science
- 1.5K Databases
- 461 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 22 Multilingual Engine
- 487 MySQL Community Space
- 3 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 416 SQLcl
- 42 SQL Developer Data Modeler
- 184.8K SQL & PL/SQL
- 21K SQL Developer
- 1.8K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.1K Development Tools
- 8 DevOps
- 3K QA/Testing
- 246 Java
- 5 Java Learning Subscription
- 10 Database Connectivity
- 66 Java Community Process
- 1 Java 25
- 9 Java APIs
- 141.1K Java Development Tools
- 6 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 10 Java SE
- 13.8K Java Security
- 3 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 124 LiveLabs
- 30 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 3 Deutsche Oracle Community
- 10 Español
- 1.9K Japanese
- 2 Portuguese
Oracle.ManagedDataAccess.Core support for ASP.NET 5
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
Answers
-
You have the following package reference:
<PackageReference Include="Oracle.ManagedDataAccess.Core" Version="2.19.91" />
The 2.19.100 version should be used instead.
-
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.
-
Can you upload a simple test case? We'll try to reproduce the problem and debug.
-
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>
-
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.
-
Oracle will publish a patched ODP.NET version on NuGet Gallery at the beginning of the new year.