code-organization

What is the best way to organize the files in your project? For example do you put all user controls in a separate folder or do you place them in a sub folder? Do you have business logic folder? A helper classes folder? I used to organize my projects like this: Project/User Controls/Module Name/ Project/Classes/Module Name/ Now I am learning more towards something like this: Project/Module Name/User Controls/ Project/Module Name/Classes/ What is the best way? Especially if the project gets really big? What type of folder structure should exist? First the purpose of folder separation is to be

My question has two parts: Does anyone have any tips or references to some documentation on the web about how to write GUI code that is easy to read, write, and maintain? Example. I find that the more extensive my GUI forms become, I end up with a long list of fairly short event handler methods. If I try to add any private helper methods, they just get lost in the shuffle, and I constantly have to scroll around the page to follow a single line of thought. How can I easily manage settings across the application? Example. If the user selects a new item in a drop-down list, I might need to enable

I am increasingly aware that my code in any single file can often span hundreds of lines quite easily and although I know the implementation might be sound, it still feels messy and unorganised. I understand that there are situations where a lot of code is neccessary, but whats the best way to organise it all? I've thought about separating variables from methods, private s from public s and internals but I don't want to because I can't help thinking that the components of ONE class belong in ONE file. This whole thing is compounded when I'm working with the codebehind of a WPF window, which

In C#, the questions of what types to create, what members they should have, and what namespaces should hold them, are questions of OO design. They are not the questions I'm interested in here. Instead, I want to ask how you store these in disk artifacts. Here are some example rules: Put all of an assembly's types in a single source file. One friend who did this said "files are an archiac code organization tool; today I use classview and Collapse to Definitions to browse my code". Put all your code in one assembly. Makes deployment & versioning simpler. Directory structure reflects namespace

Can you recommend me what should I read/learn in order to make a well organized code in C? One of the things I want to learn is the principles of splitting project in .h and .c files, what goes where and why, variable naming, when to use global variables ... I am interested in books and articles that deal with this specific problem. A good book that covers a lot of this (for both C and C++) is Large Scale C++ Software Design, by John Lakos : Also, a good rule of thumb to remember is "Never do anything that allocates memory in a header file" Regarding the files layout there are not too many