E
elziko
I have found that if Class C inherits from Class B and Class B inherits
from Class A then in a project that uses Class C I must reference the
assembly that contains Class A as well as the assembly that contains
Class B since the latter assembly will not contain all the meta data
from the former assembly.
However, is there any way that forces a project to include a reference
to assemblies contain both Class A and B when Class C (a control) is
dropped onto a form. Otherwise an error message such as:
'Public Overridable NotOverridable Property Author() As String' is
declared in project 'Company.Scope.ModuleBase.dll', which is not
referenced by project 'WindowsApplication1.exe'.
....is generated which does not make the problem immediately obvious to
the developer.
TIA
from Class A then in a project that uses Class C I must reference the
assembly that contains Class A as well as the assembly that contains
Class B since the latter assembly will not contain all the meta data
from the former assembly.
However, is there any way that forces a project to include a reference
to assemblies contain both Class A and B when Class C (a control) is
dropped onto a form. Otherwise an error message such as:
'Public Overridable NotOverridable Property Author() As String' is
declared in project 'Company.Scope.ModuleBase.dll', which is not
referenced by project 'WindowsApplication1.exe'.
....is generated which does not make the problem immediately obvious to
the developer.
TIA