Depends. You gonna use the repository on just one project, or the whole solution? lol kinda obvious answer, don't over think it. If your gonna use it in future related projects, then add it to the solution.
On Thu, Jul 9, 2009 at 8:28 AM, chrismaduro <[email protected]> wrote: > > Not for planning, I mean for the actual project files, or the whole > solution. I'm talking about source code. > > On Jul 8, 3:00 am, Processor Devil <[email protected]> wrote: > > Them both? > > Well, what means project level? > > Do you mean debug/release stages or planning the project / programming > > solution?. > > If it is the second case, then you don't need repository for planning, it > is > > better to use your standard actions because you are used to do it so. > Using > > repository is great way of sharing and updating the code, but be sure > that > > employees know how to use it properly else they will erase other's update > > and be sure that just one programmer is working just on one part and two > > programmers don't work on the same thing. > > > > 2009/7/7 chrismaduro <[email protected]> > > > > > > > > > > > > > We are moving the development team to C# and will be using a new VCS, > > > we have chosen Git. The question now is, do you create the repository > > > at the project level or the solution level. Does anyone have any > > > suggestions based on practical experience using Git with Visual Studio? >
