Ok, here is the reproduceable code (at least over here). The controls are in
one project, Form1.vb is in a separate project (one solution).
The key is, there has to be a change in the controls dll (such as adding a
Protected method to BaseInputControl.vb), that will trigger this. Not all
changes cause this behavior - so it doesn't happen with every change - but
very frequently.
BaseInputControl.vb:
Imports System.ComponentModel
Imports System.ComponentModel.Design
Imports System.Drawing.Design
Public Class BaseInputControl
Inherits UserControl
#Region " Windows Form Designer generated code "
Public Sub New()
MyBase.New()
'This call is required by the Windows Form Designer.
InitializeComponent()
'Add any initialization after the InitializeComponent() call
End Sub
'Form overrides dispose to clean up the component list.
Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)
If disposing Then
If Not (components Is Nothing) Then
components.Dispose()
End If
End If
MyBase.Dispose(disposing)
End Sub
'Required by the Windows Form Designer
Private components As System.ComponentModel.IContainer
'NOTE: The following procedure is required by the Windows Form Designer
'It can be modified using the Windows Form Designer.
'Do not modify it using the code editor.
Protected WithEvents inputCtl As System.Windows.Forms.TextBox
<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
Me.inputCtl = New System.Windows.Forms.TextBox
Me.SuspendLayout()
'
'inputCtl
'
Me.inputCtl.Location = New System.Drawing.Point(0, 0)
Me.inputCtl.Name = "inputCtl"
Me.inputCtl.Size = New System.Drawing.Size(89, 20)
Me.inputCtl.TabIndex = 0
Me.inputCtl.Text = ""
'
'BaseInputControl
'
Me.Controls.Add(Me.inputCtl)
Me.Name = "BaseInputControl"
Me.Size = New System.Drawing.Size(89, 20)
Me.ResumeLayout(False)
End Sub
#End Region
Private s As String
Protected Sub AdjustBackgroundColor()
End Sub
End Class
BaseFormInputControl.vb:
Imports System.ComponentModel
Imports System.ComponentModel.Design
Imports System.Drawing.Design
Public Class BaseFormInputControl
Inherits BaseInputControl
#Region " Windows Form Designer generated code "
'UserControl overrides dispose to clean up the component list.
Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)
If disposing Then
If Not (components Is Nothing) Then
components.Dispose()
End If
End If
MyBase.Dispose(disposing)
End Sub
'Required by the Windows Form Designer
Private components As System.ComponentModel.IContainer
'NOTE: The following procedure is required by the Windows Form Designer
'It can be modified using the Windows Form Designer.
'Do not modify it using the code editor.
<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
'
'inputCtl
'
Me.inputCtl.AcceptsReturn = True
Me.inputCtl.Name = "inputCtl"
'
'BaseFormInputControl
'
Me.Name = "BaseFormInputControl"
End Sub
#End Region
Public Sub New()
MyBase.New()
'This call is required by the Windows Form Designer.
InitializeComponent()
'Add any initialization after the InitializeComponent() call
End Sub
Public Sub test()
End Sub
Private Sub inputCtl_Validating(ByVal sender As Object, ByVal e As
System.EventArgs) Handles inputCtl.Validated
AdjustBackgroundColor()
End Sub
End Class
Form1.vb:
Public Class Form1
Inherits System.Windows.Forms.Form
#Region " Windows Form Designer generated code "
Public Sub New()
MyBase.New()
'This call is required by the Windows Form Designer.
InitializeComponent()
'Add any initialization after the InitializeComponent() call
End Sub
'Form overrides dispose to clean up the component list.
Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)
If disposing Then
If Not (components Is Nothing) Then
components.Dispose()
End If
End If
MyBase.Dispose(disposing)
End Sub
'Required by the Windows Form Designer
Private components As System.ComponentModel.IContainer
'NOTE: The following procedure is required by the Windows Form Designer
'It can be modified using the Windows Form Designer.
'Do not modify it using the code editor.
Friend WithEvents BaseFormInputControl1 As
TestControlLibrary.BaseFormInputControl
<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
Me.BaseFormInputControl1 = New TestControlLibrary.BaseFormInputControl
Me.SuspendLayout()
'
'BaseFormInputControl1
'
Me.BaseFormInputControl1.Location = New System.Drawing.Point(192, 80)
Me.BaseFormInputControl1.Name = "BaseFormInputControl1"
Me.BaseFormInputControl1.Size = New System.Drawing.Size(89, 20)
Me.BaseFormInputControl1.TabIndex = 0
'
'Form1
'
Me.AutoScaleBaseSize = New System.Drawing.Size(5, 13)
Me.ClientSize = New System.Drawing.Size(448, 266)
Me.Controls.Add(Me.BaseFormInputControl1)
Me.Name = "Form1"
Me.Text = "Form1"
Me.ResumeLayout(False)
End Sub
#End Region
End Class
CJ Taylor said:
My apologies. I did misread the post.
Wow...
Wierd question, but how many projects are in your solution... I ran into
some weird compiler errors when I had a lot of projects. I'm just pulling
straws right now I hope you know.. just trying to help.
-CJ
application,
as
then it definitely would not have had a constructor.
So again, the question is, why is the compiler complaining constantly about
not finding a constructor, making me place and remove the word 'Public'
every other compile time, in order to make it work?
Note: There may be other ways that work in getting the compiler to work
other then this trick with 'Public', I don't know. I just found an
easy
one.
"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
If you don't put an accessor on there doesn't it default it to
Friend?
In
which case doesn't your project B (second compiled) need to be in
the
same
namespace in order for that to work?
So therefore you contructor must be declared public or it doesn't think
that
a constructor is avalible for it to use.
Someone correct me if I'm wrong.
Hi, if anyone can help on this, please! This is driving me crazy.
I have a user control hierarchy several levels deep that derive for
UserControl (windows).
The class that is at the top level, has the following constructor
(generated
by VS.NET)
Public Sub New()
MyBase.New()
'This call is required by the Windows Form Designer.
InitializeComponent()
'Add any initialization after the InitializeComponent() call
End Sub
Sometimes (about half the time), when I recompile my solution (which
contains a project with this class, and a project with a form tester
trying
out this user control), I get the error I put in the subject of this
post.
Now, clearly, this class has a constructor.
If I change the code by removing the word 'Public', and recompile
everything
is great.
Next time I need to recompile, I get this error again. In this
case,
I
just
put the word 'Public' back in, and recompile - all is well again.
So I spend half my time removing 'Public' and then adding it back in -
just
to get the compiler to change its mind.
Now, it doesn't do this all the time. Sometimes it recompiles OK.
I've checked the project build order - and the project with the user
control
is compiled first.
I've tried manually compiling the first project - and then the second.
And
the second always fails, because it thinks there is no constructor
available
for the user control. Until that is, I take away or remove the 'Public'
keyword off of the constructor - in which case its fine.
Is this some ridiculous VB compiler problem? Some VS.NET bug.
Anything
I
can
do about it?
Thanks
