Project Organization - Recommendations or Best Practices

[Jordan]

I'd appreciate references to online materials presenting general
recommendations or best practices (if there are any) for organizing .NET
projects.... ideally covering things like naming conventions, custom
namespace usage, file and folder hierarchies, multi-project solutions, etc.

And, yes, I understand there is no one "right way" to do this... just
looking for some recommendations.

Thanks!

[Vinay Ahuja]

Check out this

http://blogs.msdn.com/ericgu/archive.../19/60315.aspx

The above link has links to several resources.

I recommend most of the coding conventions specified by Juval Lowy.
This is the link -
http://www.idesign.net/idesign/downl...20Standard.zip

The standards are for C#, however most of the the things are applicable for
structured coding in any language.

I have used generally <Company>.<Project>.<Module> for namespace and project
names. Some conventions say that arrange your folders and namespaces in the
same hierarchy, but I haven't found a need to do that myself.

Hope this helps.

"Jordan" wrote:

I'd appreciate references to online materials presenting general
recommendations or best practices (if there are any) for organizing .NET
projects.... ideally covering things like naming conventions, custom
namespace usage, file and folder hierarchies, multi-project solutions, etc.

And, yes, I understand there is no one "right way" to do this... just
looking for some recommendations.

Thanks!

[Michael Nemtsev]

I recomend to look at "patterns and practice" set of MS articles
http://msdn.microsoft.com/practices/...t/default.aspx
--
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do
not cease to be insipid." (c) Friedrich Nietzsche