- 3,715,500 Users
- 2,242,776 Discussions
- 7,845,368 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
ODP.NET 19.10.0 NuGet package contains a debug build
I've noticed that the assembly in the NuGet package Oracle.ManagedDataAccess version 19.10.0 (which is the latest version right now) is a debug build. That was not the case in previous versions. Could this please be changed back to a release build for the next version?
Best Answer
-
Hi Manuel,
Thanks for pointing this out. The managed ODP.NET 19.10 version is actually the release version, but is incorrectly marked as debug. My team has verified this. We do plan on fixing the issue in the next release so that developers do not mistake it as debug.
Answers
-
Hi Manuel,
Thanks for pointing this out. The managed ODP.NET 19.10 version is actually the release version, but is incorrectly marked as debug. My team has verified this. We do plan on fixing the issue in the next release so that developers do not mistake it as debug.
-
Hi,
Thanks for your answer. But are you sure that this has no effect on the runtime behavior? Because the assembly has the DebuggableAttribute with the flags "Default | DisableOptimizations" set, which means that JIT optimizations are disabled according to the documentation.
-
I'm not sure if the JIT optimizations have been disabled. The way the assembly was labelled a debug build was not done by the compiler, but by another component. Essentially, ODP.NET has debug build in its metadata, but it's actually the release build.
We will be distributing a new assembly on NuGet Gallery soon that will fix the mis-labelled assembly.