We have a solution with 29 projects including a main menu and 28 dlls. One of the projects (Project B) was created by copying an existing project (Project A), making changes including the assembly name, root namespace, form name, and internal code. When the new project (Project B) was added to the solution and a reference to it was attempted to be added to the main menu project (Project MainMenu), the new project (Project B) reference did not show up in the reference list for the main menu project. The attempt to add the reference to project B dll was done by selecting Project B from the list of projects available for reference in the Add Reference dialog. By removing the project (Project A) that had been copied from and its reference, the new project (Project B) could be added to the main menu project, but when its reference properties were viewed, the identity, description, and file path for the new project (Project B)reference were those from the copied project (Project A).
I have been unable to find anything in Project B properties that would cause Project A to be substituted for Project B in the reference list.
One further note is that Project B dll could be added from the Add Reference dialog if its dll was located through the Browse function.
Does anyone have some insight into this mystery?
--
Jim Durbin
Durbin Enterprises
VB developer
