By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,992 Members | 1,344 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,992 IT Pros & Developers. It's quick & easy.

Project Organization - Folders, Multiple Projects, etc

P: n/a
I'm starting work on a new and non trivial Windows Forms application.

What are some generally accepted recommendations for organizing the project
folders and for breaking out different parts of the applicatoin into
separate projects (i.e. multi project solution) and/or separate projects
compiled into their own DLLs and referenced by the "primary" application?

Mar 28 '06 #1
Share this Question
Share on Google+
1 Reply

P: n/a
This is a pontentially massive topic ;-)

There's so many variables that I use to determine on how to break a
project down. You say non-trivial. Does that mean you're going to be
heading for an n-tier architecture? If so I'd break each of the tiers
into seperate projects, ie UI, Business, Data Services as a minimum.
That will give you the possibility to re-use components later.

Are there going to be multiple developers working on your project?
It's important to consider how often files are going to change - the
worst thing you want is "people stepping on each other toes" and not
being able to develop if someone has a file/project checked out
exclusively via Visual Source Safe etc

Mar 29 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.