<message> This error could also be due to mixing a file reference to '<filename1>' in project '<projectname1>' with a file reference to '<filename2>' in project '<projectname2>'
<message> This error could also be due to mixing a file reference to '<filepathname1>' in project '<projectname1>' with a file reference to '<filepathname2>' in project '<projectname2>'. If both assemblies are identical, try replacing these references so both references are from the same location.
Code in your project accesses a member of another project, but the configuration of your solution does not allow the Visual Basic compiler to resolve the reference.
To access a type defined in another assembly, the Visual Basic compiler must have a reference to that assembly. This must be a single, unambiguous reference that does not cause circular references among projects.
Error ID: BC30970
To correct this error
Determine which project produces the best assembly for your project to reference. For this decision, you might use criteria such as ease of file access and frequency of updates.
In your project properties, add a reference to the file that contains the assembly that defines the type you are using.
See Also
Tasks
How to: Add or Remove References in Visual Studio (Visual Basic)
How to: Modify Project Properties and Configuration Settings
Troubleshooting Broken References
Concepts
Resolving a Reference When Multiple Variables Have the Same Name