Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
error using oracle.manageddataaccess.client in a WPF application
hi,
we are having issues with a WPF-MVVM application using Oracle.ManagedDataAccess.Client. We have installed oracle.manageddataaccess.dll, release 12.1.0.1.0 on a developer computer with Windows 7 64 bit OS, Microsoft Visual Studio 2013 and Microsoft .NET Framework 4. Installation seems to be ok, and oracle.manageddataaccess.dll results to be registered in c:\windows\microsoft .net\assembly\GAC_MSIL. But when we try to compile the app, the following errors occurs
Error 175: The ADO.NET provider with invariant name 'Oracle.ManagedDataAccess.Client' is either not registered in the machine or application config file, or could not be loaded
errors are caused by the Entity Data Model files (there is an error for each .edmx file).
notice that the app works on another computer having the same configuration, so I guess the problem is due to some wrong setting on the computer
any idea?
Best Answer
-
hi,
at last we fixed the issue! simply, we uninstalled and reinstalled Visual Studio and Oracle.manageddataaccess in this order. Now it works. thank you
Answers
-
Error 175 usually indicates a problem with the <DbProviderFactories> section of your machine.config or app/web.config file. Compare the settings and XML between the computer that's working and not working.
-
hi,
at last we fixed the issue! simply, we uninstalled and reinstalled Visual Studio and Oracle.manageddataaccess in this order. Now it works. thank you