markmcl
10-19-2007, 09:55 AM
I think I found a bug in the CLR
Note: this is all in .Net 1.1 Visual Studio 2003
Situation:
- A VB Project (p1) References a C# project (p2) that references a VB project (p3).
- All project references
p1 = vb web project
p2 = c# library
p3 = vb library
From p1, you are able to reference objects defined in p2.
From p1, you are able to reference objects defined in p3.
But from p1 you are unable to reference a p3 object defined in p2.
One solution:
When I change the p1 reference to p3 to a hard reference (not a project reference) everything works fine. Leads me to believe that the project types / solution structure in this case hits a bug in the CLR.
Note: this is all in .Net 1.1 Visual Studio 2003
Situation:
- A VB Project (p1) References a C# project (p2) that references a VB project (p3).
- All project references
p1 = vb web project
p2 = c# library
p3 = vb library
From p1, you are able to reference objects defined in p2.
From p1, you are able to reference objects defined in p3.
But from p1 you are unable to reference a p3 object defined in p2.
One solution:
When I change the p1 reference to p3 to a hard reference (not a project reference) everything works fine. Leads me to believe that the project types / solution structure in this case hits a bug in the CLR.