- 3,716,000 Users
- 2,242,928 Discussions
- 7,845,734 Comments
Forum Stats
Discussions
Categories
- 17 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 1.6K Databases
- 476 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 22 Multilingual Engine
- 487 MySQL Community Space
- 5 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 417 SQLcl
- 42 SQL Developer Data Modeler
- 184.9K SQL & PL/SQL
- 21K SQL Developer
- 1.9K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.1K Development Tools
- 9 DevOps
- 3K QA/Testing
- 256 Java
- 6 Java Learning Subscription
- 10 Database Connectivity
- 67 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
- 125 LiveLabs
- 30 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 3 Deutsche Oracle Community
- 11 Español
- 1.9K Japanese
- 2 Portuguese
NuGet PackageReferences doesn't work with Oracle.ManagedDataAccess.EntityFramework
Following this tutorial:
http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/dotnet/2015/NuGet/NuGet.html#overview
with VS 2017 and PackageReferences instead of packages.config. It fails to download the dependent packages, and also doesn't change app.config.
It works for VS 2017 when you select the packages.config method though.
Answers
-
Do you mind sharing how you have configured your PackageReference node?
-
What do you mean?
I have turned the PackageReferences feature on in VS -> Tools -> NuGet.
I select "PackageReferences" when VS prompts me when adding the first NuGet reference to the project.
Other than that I haven't configured anything.
-
I'm not a NuGet expert, but I looked into this. It appears these are "features" of PackageReferences (PR). Microsoft has documented PR do not make changes to .NET config files, unlike packages.config
https://docs.microsoft.com/en-us/nuget/create-packages/source-and-config-file-transformations
Dependent package references appear to require adding them in explicitly with PR.
https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files
I tried another popular NuGet package with an assembly dependency, just like ODP.NET EF. I observed the same behavior in that dependent references were not added. However, dependent packages were actually downloaded locally.
Again, I'm not a NuGet expert. Corrections are welcome.
-
It's sad if NuGet really has that limitation.
The workaround for the user would be to create the project using packages.config, then use a migration tool to convert the project to PackageReferences.
The tutorial should probably be updated to reflect this.
-
The tutorial you link to uses VS 2015. I don't believe NuGet PR is supported in VS 2015.
-
"Before starting this tutorial, you should:
- Install Microsoft Visual Studio 2015 or later with .NET Framework 4 or later."
-
Nowhere in the tutorial does it ask you to change the default behavior to PackageReferences. By following the tutorial instructions as written, you will successfully complete the lab.