Where to put everything?

Question

0.00/5 (No votes)

See more:

Dear All

Since I'm new in the world of oop and vb.net I would like to ask you a simple question.

I hear about classes being the blueprints of objects etc but I couldn't find any information on how to structure a program.

Should I create a .dll and put all my classes in, calling it from my main program and using the objects from there?
Should I create a project, create all classes needed in the main program and compile the whole thing to a .exe?
Should I use another technic?

How should my program be architecture? :doh:

Posted 21-Sep-10 7:53am

Perifanos73

Add a Solution

Comments

Rajesh Sajjanar 21-Sep-10 14:03pm

Too many questions, dont confuse yourself, can you ask one questions at a time so that user can help you

3 solutions

Solution 1

But there is only one question.

What is the proper way of architecturing a program?

Posted 21-Sep-10 8:16am

Perifanos73

Solution 3

ok, thanks for your answer.

To extend my question a little bit, how about modules...
When and where should one use them, if one should use them at all...

Best Regards

Posted 21-Sep-10 10:47am

Perifanos73

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Marc A. Brown · Accepted Answer · 2010-09-21T09:44:00

Solution 2

Are you writing classes that would be useful for more than one project? If so, putting those classes into a library (DLL) would make sense. If your classes are specific to your project, creating a separate library for them may not make much sense, in which case you'd include them in the executable project instead.

Posted 21-Sep-10 9:44am

Marc A. Brown

Comments

Perifanos73 21-Sep-10 17:14pm

Reason for my vote of 5
Automatic vote of 5 for accepting answer.