“Reference could not be resolved” error when validating your architecture using Visual Studio architecture modeling tools
Apr 7, 2015Importer

Summary
This post addresses a specific issue where architecture validation in Visual Studio 2012 and 2013 fails due to primary reference resolution errors when the reference is built against a higher .NET Framework version than the targeted framework. A workaround is provided by editing the modeling project file to set `<ResolveAssemblyReferenceIgnoreTargetFrameworkAttributeVersionMismatch>true</ResolveAssemblyReferenceIgnoreTargetFrameworkAttributeVersionMismatch>`.
More from the Code Dependency Visualization and Layer Validation trail
- Live Dependency Validation in Visual Studio 2017
- Live architecture dependency validation in Visual Studio “15” Preview 5
- CodeLens Indicator for Code Health
- Code Map: From Visual Studio 2013 Ultimate to Visual Studio 2015 Enterprise
- Code Maps improvements in Visual Studio Enterprise 2015 RTM: Code maps now have simpler menus, more intuitive icons, and independent group layout