Directory Structure for a Small Library?

No need to store compiled DLLs For hosting: try CodePlex and Google Code.

No need to store compiled DLLs. For hosting: try CodePlex and Google Code.

– Roman A. Taycher Aug 6 '10 at 5:08 Roman, take for example this structure: code.google.Com/p/extsharp/source/browse - Browse the trunk folder and see for yourself how this project is organized. "In general", this is the structure of a project that will be available through a SVN repository.

People will check out this code (download it to their machines) using a SVN tool as Tortoise tortoisesvn.net. Remember that there's no recipe that fits all projects. So, depending on your project structure you can have more or less folders, etc. Your idea of separating tests, libraries and license stuff is a really good one.

– Leniel Macaferi Aug 6 '10 at 15:27.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions