I've seen a couple of threads on this but not enough for a definitive conclusion.
I'm trying to define a standard practice for source controlling a flex and back-end project (namely flex -> remoting -> .net ( -> sql?) Do people tend to treat their server-side projects as a separate project in a separate repository? With everything in the one repository you can keep local compilation consistent and check-in build scripts, however by splitting up into multiple projects you're keeping flexibilty and managability by not bloating your repository. I guess it'll come down to preference but was just wondering what others are doing, as a general rule our developers currently will be dealing with both client side and server side projects but down the line i'd like to see clearer separation of roles. Any thoughts or practices people can throw in would be much appreciated. Dan -- http://danny-t.co.uk
