Saving code for later use

D

Denaes

Well-known member
Joined
Jun 10, 2003
Messages
956
Whats the best practice for this?

Ive always heard that anything you want to use over and over, you create a class.

Even if its just a single subroutine, start a class for it, then may end up adding more to it later.

Of course this was tought to me in my OOP course on Java, not at all using VB.Net.

Does VS.Net 2003 have any sort of way to save a single copy of classes?

Can you designate a single directory as your "Class Vault"?

One thing I know about classes, especially if theyre evolving (youre debugging, updating, etc), you want one copy. You dont want to have 8 copies floating around. Maybe an origional and a working, but not more than that.

So having the classes all in one directory seems the best practice.

Id assume the same would go with controls as well. Any control you create, you can compile into a .dll and throw it in your "Controls" directory. If you change it (add more functionality) then replace it. If you actually change procedures, you might want to provide overriden methods so that one app youre working on doesnt all of the sudden start working differently or get broken.

Any opinions or thoughts on this practice? VS.Net have anything to help this out at all?
 
Denaes said:
Whats the best practice for this?
[snip]
Any opinions or thoughts on this practice? VS.Net have anything to help this out at all?
Click to expand...

Well, I am new to the VS IDE, but, I create solutions that have the referenced assembly projects added as well as the project I am working on. Still only one copy of the Referenced project.

But if anyone could recommend a good book on using the VS 2003 IDE I would appreciate it.

joe
 
Joe Mamma said:
Well, I am new to the VS IDE, but, I create solutions that have the referenced assembly projects added as well as the project I am working on. Still only one copy of the Referenced project.

But if anyone could recommend a good book on using the VS 2003 IDE I would appreciate it.

joe
Click to expand...

I remember in Java (or the IDE I was using in my Java class anyway) you could set a directory/s which were considered shared classes and would be available for you to code without importing them into your project.

Handy, yes. But a huge pain in the if youre developing on more than one machine to make sure that youre synched up with the same classes.
 
Back
Top