The "big picture" here is that I'm wondering what it is *specifically* about
[setting a reference] that enables my application (e.g., Project_A.exe) to
recognize and consume the types located in referenced assemblies.
Suppose I have Project_A (Windows Forms application) opened in Visual Studio
and I set a reference to two other assemblies:
1. Project_B (which is a class library project included in the same solution
as Project_A)
2. Library_C (which is a .NET class library on the local machine, but for
which we do not have the VS project)
What changes happen in the assembly or project metadata for Project_A for
each of the two references described above?
I understand that I can open the .csproj and/or the .sln files and see
additional entries per the references ---but what is different about the
compiled assembly (Project_A.exe) for having the references (vs not having
the references)?
Thanks.