Reputation: 1493
We have a Asp.net webforms webapplication. The solution has the following structure:
- MySolution\
- MySolution.Main\
- MySolution.Web\
- MySolution.sln
Is there a best practice how to structure the trunk directory? Put the solution directory in the trunk or the content of the solution direcotry? Build a new structure under trunk?
Edit:
I think I take the following structure:
trunk\
doc\
lib\
src\
MySolution.Main\
MySolution.Web\
Mysolution.sln
In this case I have the sln file directly under the trunk. Is that a good idea?
Upvotes: 0
Views: 195
Reputation: 7915
I would put it in a separate directory, calling it src\
for example. Like this you can create additional directories for documentation and other stuff.
Example:
trunk\
src\
MySolution.Main\
MySolution.Web\
MySolution.sln
doc\
Suggestion: Take a look at http://codeplex.com, it might be a reference point on how some popular projects are structured.
Upvotes: 1
Reputation: 6803
we were faced with this dilema and what we did is pretty much what you have done. We did not start out this way we had a massive solution that needed seperating out into products.
And after we had done that and got rid of the chaff we found we were left with a structure much like you are describing, he had a directory called src under trunc and then the structure you describe
One thing to watch is do not commit bin or .suo files these are generated each time and it is a mistake to commit them.
Don't whatever you do invent a totally new structure stick with the standard trunk, tags, branches structure as this is most definately best practise.
Upvotes: 0