<div>
Hi Bob,<br />
<br />
Noticed this is still open.<br />
<br />
Just for your knowledge. Have removed DefInstance by Form1.DefInstance with m_Form1.<br />
<br />
Public m_Form1 As Form1<br />
<br />
and then <br />
<br />
m_Form1 = New Form1<br />
<br />
Thanks as always for your help 
</div>


Hi Bob,

Noticed this is still open.

Just for your knowledge. Have removed DefInstance by Form1.DefInstance with m_Form1.

Public m_Form1 As Form1

and then

m_Form1 = New Form1

Thanks as always for your help

<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
Thanks for clicking.<br />
<br />
I've converted over my appication from vb6 to vb.net.<br />
<br />
As part of the upgrade wizard it uses DefInstance property to reference controls within a form from outside that form.<br />
<br />
I've hit problems with DefInstance when initializing a new instance of a form. In short it ends up in a repeating loop due to the initialisation of the form calling DefInstance for a control before form has been initialized properly<br />
<br />
Is there a way around using DefInstance?? How are controls referenced from outside that form if creating vb.net project from new.
</div>
</div>


Hi,

Thanks for clicking.

I've converted over my appication from vb6 to vb.net.

As part of the upgrade wizard it uses DefInstance property to reference controls within a form from outside that form.

I've hit problems with DefInstance when initializing a new instance of a form. In short it ends up in a repeating loop due to the initialisation of the form calling DefInstance for a control before form has been initialized properly

Is there a way around using DefInstance?? How are controls referenced from outside that form if creating vb.net project from new.

Upgrade Wizard issues - DefInstance!!

The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.