DefInstance

#1 07-26-2002, 02:51 PM

Do you guys think it's good practice to remove the DefInstance functions in an upgraded VB net program? Why did Microsoft remove the ability to access "default forms"?

**Derek Stone** · #2 07-26-2002, 03:48 PM

They had no choice but to remove them. .NET doesn't support them. Simple as that.

And yes, if you have the time to make the proper changes I would remove the DefInstance functions, although they shouldn't cause any problems as they stand.

**divil** · #3 07-28-2002, 04:34 AM

Microsoft didn't remove the ability per se, you just have to understand that in VB.NET you have Classes, and you have Structures. There is no special case for forms as there was previously. A "form" is just a class with some pre-written code.

You can't just get a default instance of a class, that's what Shared members are for. I hope that makes it clearer.

#4 07-30-2002, 01:57 PM

Is it then also bad practice to use global variables in Modules?

**Derek Stone** · #5 07-30-2002, 02:31 PM

~~There are no modules in .NET.~~

(see below)

#6 07-30-2002, 05:29 PM

Yes there are modules in .NET. I'm using some right now!?

**Derek Stone** · #7 07-30-2002, 05:54 PM

I stand corrected. My apologies.

And yes, it is a bad practice if you want to adhere to strict OOP standards.