Hi

I have several classes. Should I keep them as separate class files or can I
keep them all in a single file?

Thanks

Regards

Hello,

"John" <(E-Mail Removed)> schrieb:
> I have several classes. Should I keep them as separate class
> files or can I keep them all in a single file?

Every class should be kept in a separate file (except nested classes).

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
http://www.mvps.org/dotnet

Whatfor can you put many classes in one file at a time? I thought it was
just help for the programmer, so that he can organize his classes better.
But as it sounds there is another reason for that. What is the reason?
I usually create a new file for each class.

Thanx for help,

BigMomma

"John" <(E-Mail Removed)> schrieb
> I have several classes. Should I keep them as separate class files or
> can I keep them all in a single file?

I prefer separate files, but it's also possible to keep some in the same
file.


--
Armin

As others have said, it really boils down to a matter of choice, however it
could be helpful to group classes together by topic. e.g.:
Classes relating to forms in one file
Classes releating to ADO.Net in another file
etc.

"BigMomma" <(E-Mail Removed)> wrote in message
news:bjivll$215$01$(E-Mail Removed)...
> Whatfor can you put many classes in one file at a time? I thought it was
> just help for the programmer, so that he can organize his classes better.
> But as it sounds there is another reason for that. What is the reason?
> I usually create a new file for each class.
>
> Thanx for help,
>
> BigMomma
>
>

Hello,

"Stephany Young" <(E-Mail Removed)> schrieb:
> As others have said, it really boils down to a matter of choice,
> however it could be helpful to group classes together by
> topic. e.g.:
> Classes relating to forms in one file
> Classes releating to ADO.Net in another file

In VS.NET, you can group the classes in folders. There is IMHO no need
to put more than one class (except nested classes) into a single file.

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
http://www.mvps.org/dotnet

Hello,

"BigMomma" <(E-Mail Removed)> schrieb:
> I usually create a new file for each class.

\\\
Public Class Foo
Public Class Bar

Yes, however the point is that if one want's to then one can - It is a
matter of choice.

"Herfried K. Wagner [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello,
>
> "Stephany Young" <(E-Mail Removed)> schrieb:
> > As others have said, it really boils down to a matter of choice,
> > however it could be helpful to group classes together by
> > topic. e.g.:
> > Classes relating to forms in one file
> > Classes releating to ADO.Net in another file
>
> In VS.NET, you can group the classes in folders. There is IMHO no need
> to put more than one class (except nested classes) into a single file.
>
> --
> Herfried K. Wagner
> MVP · VB Classic, VB.NET
> http://www.mvps.org/dotnet
>
>

Hello,

"Stephany Young" <(E-Mail Removed)> schrieb:
> Yes, however the point is that if one want's to then one
> can - It is a matter of choice.

You are right. Nevertheless, there are a lot of VB.NET programmers who
do not know that classes can be grouped in folders.

;-)

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
http://www.mvps.org/dotnet

Stephany,
> Yes, however the point is that if one want's to then one can - It is a
> matter of choice.
Yes you have the choice of putting two forms in one file.

However! be warned if you make this choice, then you will no longer be able
to design the forms in VS.NET!

I do agree with you, one of the nice benefits of VB.NET over VB6 is that I
can put any number of types in a single source file! By type I mean Class,
Module, Structure, Delegate, or Enum. In fact I can put any number of
namespaces in a single source file. Lately I'm finding I limit one class,
module or structure to a source file, however I will group many Delegates &
Enums in a single source file. Either with the class or structure that they
are closely associated with or a common file, if they are related to a group
of classes, modules, or structures. Except for nested classes, which are
implementation details any way...

Hope this helps
Jay

"Stephany Young" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Yes, however the point is that if one want's to then one can - It is a
> matter of choice.
>
> "Herfried K. Wagner [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hello,
> >
> > "Stephany Young" <(E-Mail Removed)> schrieb:
> > > As others have said, it really boils down to a matter of choice,
> > > however it could be helpful to group classes together by
> > > topic. e.g.:
> > > Classes relating to forms in one file
> > > Classes releating to ADO.Net in another file
> >
> > In VS.NET, you can group the classes in folders. There is IMHO no need
> > to put more than one class (except nested classes) into a single file.
> >
> > --
> > Herfried K. Wagner
> > MVP · VB Classic, VB.NET
> > http://www.mvps.org/dotnet
> >
> >
>
>