Feedback
Did this article resolve your question/issue?

   

Article

"No exports were found that match the constraint: ContractName" error with Oracle ADO.NET provider

Information

 
Title"No exports were found that match the constraint: ContractName" error with Oracle ADO.NET provider
URL NameNo-exports-were-found-that-match-the-constraint-ContractName-error-with-Oracle-ADO-NET-provider
Article Number000185083
EnvironmentProduct: Connect for ADO.NET Oracle provider
Version; 4.1
OS: Windows
Database: Oracle
Application: Visual Studio 2013
Question/Problem Description
The below error is received.
Steps to Reproduce
Clarifying Information
Error MessageCannot load "...\GISModel.edmx": No exports were found that match the constraint: ContractName
Defect Number
Enhancement Number
Cause
Resolution
Clear the Visual Studio 2013 Component Model Cache by renaming the following folder or deleting the content of this folder;

AppData%\..\Local\Microsoft\VisualStudio\12.0\ComponentModelCache
Workaround
Notes
Last Modified Date5/11/2016 6:41 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.