Structure of Projects in Version Control

Question

I know there are at least 10 different ways to structure project in version control. I\'m curious what some methods being used are and which ones work for you. I\'ve worked

Answer 1

What about external dependencies such a the AJAXTookit or some other 3rd party extension that's used on several projects?

Source control is for source code, not binaries. Keep any 3rd party assemblies/jars in a separate repository. If you're working in the Java world try something like Maven or Ivy. For .Net projects a simple shared drive can work well as long as you have decent policies around how it's structured and updated.