MSB3268: The primary reference "{0}" could not be resolved because it has an indirect dependency on the framework assembly "{1}" which could not be resolved in the currently targeted framework. "{2}". To resolve this problem, either remove the reference "{0}" or retarget your application to a framework version which contains "{1}".
MSB3261: The FrameworkDirectory metadata must be set on all items passed to the FullFrameworkAssemblyTables parameter. The ...
MSB3262: When targeting a profile the ProfileName parameter and one of FullFrameworkFolders or FullFrameworkAssemblyTables ...
MSB3263: The file "{0}" will be ignored because it cannot be read. This file was either passed in to FullFrameworkAssemblyTables ...
MSB3267: The primary reference "{0}", which is a framework assembly, could not be resolved in the currently targeted framework. ...
MSB3268: The primary reference "{0}" could not be resolved because it has an indirect dependency on the framework assembly ...
MSB3270: There was a mismatch between the processor architecture of the project being built "{0}" and the processor architecture ...
MSB3271: There was a mismatch between the processor architecture of the project being built "{0}" and the processor architecture, ...
MSB3273: Unknown processor architecture. The implementation file "{0}" for "{1}" had an ImageFileMachine value of "0x{2}". ...
MSB3274: The primary reference "{0}" could not be resolved because it was built against the "{1}" framework. This is a higher ...