Put this code in a Class?

[=?Utf-8?B?RU1hbm5pbmc=?=]

I'm very new to VB.Net and am struggling with the concept of classes and when
to use them. I have found some coding to email exceptions to myself that
might occur in this project I'm developing. I would like to make this coding
available to other projects that I will be developing in the future. Should
this coding go into a class? Actually I've done this already and it seems to
work pretty slick. I linked the class to my project and I assume I can link
it to other projects (but I haven't tried that yet).

Is a class the best place for this kind of code? If not, what is?

Thanks for any help or advice.

[Tom Shelton]

On 2007-12-12, EManning <EM******@discussions.microsoft.comwrote:

I'm very new to VB.Net and am struggling with the concept of classes and when
to use them. I have found some coding to email exceptions to myself that
might occur in this project I'm developing. I would like to make this coding
available to other projects that I will be developing in the future. Should
this coding go into a class? Actually I've done this already and it seems to
work pretty slick. I linked the class to my project and I assume I can link
it to other projects (but I haven't tried that yet).

Is a class the best place for this kind of code? If not, what is?

Thanks for any help or advice.

If you want to use it in multiple projects, then I would suggest making
it a public class in a class library project... Then you just have to
reference the dll, in any project you want to use it from, and it's
available to you.

--
Tom Shelton

[=?Utf-8?B?RU1hbm5pbmc=?=]

This might be a dumb question but a "class library project" would be a
project that contains several classes, all of which could be accessed by
other projects. Correct?

Thanks for your help, Tom.

"Tom Shelton" wrote:

On 2007-12-12, EManning <EM******@discussions.microsoft.comwrote:

I'm very new to VB.Net and am struggling with the concept of classes and when
to use them. I have found some coding to email exceptions to myself that
might occur in this project I'm developing. I would like to make this coding
available to other projects that I will be developing in the future. Should
this coding go into a class? Actually I've done this already and it seems to
work pretty slick. I linked the class to my project and I assume I can link
it to other projects (but I haven't tried that yet).

Is a class the best place for this kind of code? If not, what is?

Thanks for any help or advice.

If you want to use it in multiple projects, then I would suggest making
it a public class in a class library project... Then you just have to
reference the dll, in any project you want to use it from, and it's
available to you.

--
Tom Shelton

[Tom Shelton]

On 2007-12-12, EManning <EM******@discussions.microsoft.comwrote:

This might be a dumb question but a "class library project" would be a
project that contains several classes, all of which could be accessed by
other projects. Correct?

Thanks for your help, Tom.

Yep. You've got it.

--
Tom Shelton

[schneider]

Some other things to think about while building a DLL/Class Library.

Keep in mind the scope of classes, subs, functions. Make things private,
friend, protected, and only public when needed.
Using MS FXCop against your code and reading about the items flagged can
help you learn a lot...

I would read a few atricles on OO:

Introduction to VB.NET Object Oriented
http://www.ondotnet.com/pub/a/dotnet...oo.html?page=1

Schneider


"EManning" <EM******@discussions.microsoft.comwrote in message
news:0F**********************************@microsof t.com...

I'm very new to VB.Net and am struggling with the concept of classes and
when
to use them. I have found some coding to email exceptions to myself that
might occur in this project I'm developing. I would like to make this
coding
available to other projects that I will be developing in the future.
Should
this coding go into a class? Actually I've done this already and it seems
to
work pretty slick. I linked the class to my project and I assume I can
link
it to other projects (but I haven't tried that yet).

Is a class the best place for this kind of code? If not, what is?

Thanks for any help or advice.

[=?Utf-8?B?RU1hbm5pbmc=?=]

Thanks everyone for your replies. I have trouble understanding the
difference between classes and functions and where to use them. Maybe I'll
understand better after I've used classes for a while.

Thanks again.
"schneider" wrote:

Some other things to think about while building a DLL/Class Library.

Keep in mind the scope of classes, subs, functions. Make things private,
friend, protected, and only public when needed.
Using MS FXCop against your code and reading about the items flagged can
help you learn a lot...

I would read a few atricles on OO:

Introduction to VB.NET Object Oriented
http://www.ondotnet.com/pub/a/dotnet...oo.html?page=1

Schneider


"EManning" <EM******@discussions.microsoft.comwrote in message
news:0F**********************************@microsof t.com...

I'm very new to VB.Net and am struggling with the concept of classes and
when
to use them. I have found some coding to email exceptions to myself that
might occur in this project I'm developing. I would like to make this
coding
available to other projects that I will be developing in the future.
Should
this coding go into a class? Actually I've done this already and it seems
to
work pretty slick. I linked the class to my project and I assume I can
link
it to other projects (but I haven't tried that yet).

Is a class the best place for this kind of code? If not, what is?

Thanks for any help or advice.