Public Variables

[thomasp]

Variables that I would like to make available to all forms and modules in my
program, where should I declare them? At the momment I just created a
module and have them all declared public there. What is the normal way to
do this?

Thanks,

Thomas

--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.c om<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

[m.posseth]

well i believe you do it just right , i also use a module for that , however
with one slight twist i use Friend instead of public in VB.Net modules

regards

M. Posseth [MCP]

<th*****@msala. net> wrote in message
news:43******** **************@ news.newsdemon. com...

Variables that I would like to make available to all forms and modules in
my
program, where should I declare them? At the momment I just created a
module and have them all declared public there. What is the normal way to
do this?

Thanks,

Thomas

--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.c om<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

[thomasp]

Thanks for the quick answer. I have been using VB2005 for about a month
now. I have never used Friend, but I will look it up and read about it.

Thomas

--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.c om<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

[Scott M.]

You declare them in a standard Module and make that Module the project's
startup item.

Friend level scope makes the item accessible anywhere IN the assembly.
Public scope makes the item accessible anywhere INSIDE or from OUTSIDE the
assembly.
<th*****@msala. net> wrote in message
news:43******** **************@ news.newsdemon. com...

Thanks for the quick answer. I have been using VB2005 for about a month
now. I have never used Friend, but I will look it up and read about it.

Thomas

--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.c om<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

[Sathyaish]

> You declare them in a standard Module and make that Module the project's
startup item.

Scott M.,

Please correct me if I am wrong, but I am not sure if you *have* to set
the module as the start up object. That information might be misleading
to the OP. In my opinion, even if you do not set a module as a start up
object, and it is not an object module, meaning it is a standard
module, then the variable declared as public in that module will be
accessible globally throughout.

The scope of accessibility, of course, as you mentioned, will be global
if it is public and assembly scope, if it is friend.

Regards,
Sathyaish

[Scott M.]

You are correct that the standard Module need not be set as the Startup
Object in the project. I still recommend that it be set that way, as it is
more self-documenting in terms of programmatic flow.

"Sathyaish" <sa*******@gmai l.com> wrote in message
news:11******** *************@g 49g2000cwa.goog legroups.com...

You declare them in a standard Module and make that Module the project's

startup item.

Scott M.,

Please correct me if I am wrong, but I am not sure if you *have* to set
the module as the start up object. That information might be misleading
to the OP. In my opinion, even if you do not set a module as a start up
object, and it is not an object module, meaning it is a standard
module, then the variable declared as public in that module will be
accessible globally throughout.

The scope of accessibility, of course, as you mentioned, will be global
if it is public and assembly scope, if it is friend.

Regards,
Sathyaish

[Bob Powell [MVP]]

This might have been de-rigeur in the days of VB6 but VB.NET is an object
oriented language and there is no good excuse for a public variable anywhere
in such a system. They cause endless problems and should be avoided like the
plague.

Variables should always be private and accessed through correctly structured
get/set accessor properties.

In certain, very limited cases, you can use the shared keyword to provide
methods and properties that are globally available. These should however be
completely self-contained and not rely on any stored data such as a static
method referring to a static property and other such bad habits. The Math
class is the perfect example of where the Shared keyword is properly used.

If you want to develop good OOP techniques throw out just about everything
you learned from VB6.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

<th*****@msala. net> wrote in message
news:43******** **************@ news.newsdemon. com...

Variables that I would like to make available to all forms and modules in
my
program, where should I declare them? At the momment I just created a
module and have them all declared public there. What is the normal way to
do this?

Thanks,

Thomas

--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.c om<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

[Herfried K. Wagner [MVP]]

"Scott M." <s-***@nospam.nosp am> schrieb:

You are correct that the standard Module need not be set as the Startup
Object in the project. I still recommend that it be set that way, as it
is more self-documenting in terms of programmatic flow.

In this case I prefer selecting 'Sub Main' as startup object. However, the
decision is up tp personal preference...

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Dennis]

I have a form (Form2) which has a lot of overhead when it first loads so I
have a module containing sub main from which I start my application. In this
module, I declare a global variable for Form2 as below since it's shown as a
dialog in several places in my "mainform" as well as from otherr forms that I
show as dialogs from "mainform"

public myForm2 as Form2

sub main
'Show Splash screen
myForm2 = new Form2
'Close Splash screen
mainform.show
Application.Run ()
end sub

I find using the global variable myForm2 a lot easier and faster than trying
to declare the myForm2 in "mainform" then passing it as a property to other
forms that use myForm2 that are called as dialogs from "mainform"

How would you do it and yet retain the speed of only having to load Form2
once while a splash screen is showing.
--
Dennis in Houston
"Bob Powell [MVP]" wrote:

This might have been de-rigeur in the days of VB6 but VB.NET is an object
oriented language and there is no good excuse for a public variable anywhere
in such a system. They cause endless problems and should be avoided like the
plague.

Variables should always be private and accessed through correctly structured
get/set accessor properties.

In certain, very limited cases, you can use the shared keyword to provide
methods and properties that are globally available. These should however be
completely self-contained and not rely on any stored data such as a static
method referring to a static property and other such bad habits. The Math
class is the perfect example of where the Shared keyword is properly used.

If you want to develop good OOP techniques throw out just about everything
you learned from VB6.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

<th*****@msala. net> wrote in message
news:43******** **************@ news.newsdemon. com...

Variables that I would like to make available to all forms and modules in
my
program, where should I declare them? At the momment I just created a
module and have them all declared public there. What is the normal way to
do this?

Thanks,

Thomas

--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.c om<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

[Scott M.]

This is where "Friend" level scope becomes useful. Public means that the
variable is available from anywhere within the assembly
as well as by external assmeblies that reference the first one.

Friend level scope means that the variable can be called by any code within
the assembly only.

"Dennis" <De****@discuss ions.microsoft. com> wrote in message
news:8E******** *************** ***********@mic rosoft.com...

I have a form (Form2) which has a lot of overhead when it first loads so I
have a module containing sub main from which I start my application. In
this
module, I declare a global variable for Form2 as below since it's shown as
a
dialog in several places in my "mainform" as well as from otherr forms
that I
show as dialogs from "mainform"

public myForm2 as Form2

sub main
'Show Splash screen
myForm2 = new Form2
'Close Splash screen
mainform.show
Application.Run ()
end sub

I find using the global variable myForm2 a lot easier and faster than
trying
to declare the myForm2 in "mainform" then passing it as a property to
other
forms that use myForm2 that are called as dialogs from "mainform"

How would you do it and yet retain the speed of only having to load Form2
once while a splash screen is showing.
--
Dennis in Houston
"Bob Powell [MVP]" wrote:

This might have been de-rigeur in the days of VB6 but VB.NET is an object
oriented language and there is no good excuse for a public variable
anywhere
in such a system. They cause endless problems and should be avoided like
the
plague.

Variables should always be private and accessed through correctly
structured
get/set accessor properties.

In certain, very limited cases, you can use the shared keyword to provide
methods and properties that are globally available. These should however
be
completely self-contained and not rely on any stored data such as a
static
method referring to a static property and other such bad habits. The Math
class is the perfect example of where the Shared keyword is properly
used.

If you want to develop good OOP techniques throw out just about
everything
you learned from VB6.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

<th*****@msala. net> wrote in message
news:43******** **************@ news.newsdemon. com...

>
> Variables that I would like to make available to all forms and modules
> in
> my
> program, where should I declare them? At the momment I just created a
> module and have them all declared public there. What is the normal way
> to
> do this?
>
> Thanks,
>
> Thomas
>
> --
> Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
> ------->>>>>>http://www.NewsDemon.c om<<<<<<------
> Unlimited Access, Anonymous Accounts, Uncensored Broadband Access