Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, June 23, 2017 3:36 AM
I am running a Visual Studio application(on Visual Studio 2015 and 2017 Community Editions), and have run into the following outcome which terminates the run;
No exports were found that match the constraint:
ContractName MONAHRQ
RequiredTypeIdentity Monahrq.Sdk.DataProvider.IDatabaseCreator
I have read a lot of comments that proposes a fix of renaming or deleting the following "C:\Users\xxx\AppData\Local\Microsoft\VisualStudio\ 15.0_f9a40a22 \ ComponentModelCache "
This troubleshooting has not worked for me. I’d appreciate some help here. Thanks.
All replies (1)
Monday, June 26, 2017 3:04 AM
Hi EKAE,
Welcome to the MSDN forum.
>> No exports were found that match the constraint:
Refer to the error message, you can have a try with the following:
- Go to Control Panel-Programs and Features, right click the VS 2015 and choose Change-Repair, for VS 2017 you need to re-run the Visual Studio Installer and click the icon beside ‘Launch’ and select ‘Repair’
- Clear all folders and files under the folder: %LocalAppData%\Microsoft\VisualStudio\14.0\ and %LocalAppData%\Microsoft\VisualStudio\15.0_f9a40a22, restart the VS 2015 or VS 2017 to check it again.
- Open cmd and navigate to the VS 2015/2017 installation folder like C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE and run the command: devenv /safemode to run it as safe mode, then check if the installed extensions caused tis issue.
Meanwhile, you can have a look at this similar issue: Error message “No exports were found that match the constraint contract name” and some other solutions were mentioned and you can have a try to troubleshoot this issue, thank you for your cooperation.
Best regards,
Sara
MSDN Community Support<br/> Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact <a href="mailto:[email protected]">[email protected]</a>.