On Tue, 2010-03-23 at 02:09 -0700, Anders wrote: > I admit that the "dbg" in the folder name threw me off at first. But > if you really wanted to use the VS convention, then the bin-folder > should remain within the project folder and then, i guess, you would > have to go to the DbMetal folder to find all the dlls in one place.
Right. Plus there would be lots of duplicate files -- every project would have it's own DbLinq.dll assembly, each of the test projects would need copies of both DbLinq.dll and DbLinq.PROVIDER.dll, etc., etc. At one point, iirc, there were ~13 different copies of DbLinq running around after a full build. Having toplevel build/build.dbg directories was seen as the solution to all this duplication (which was also slowing down the build, as MSBuild would keep making all these copies...) (For the life of me, I can't imagine why VS prefers per-project output directories. Per-solution makes far more sense...) > Personally, I don't particularly like the files being two levels down > (e.g. bin/Debug) and on the other hand wouldn't like Release and Debug > on the top level, so I guess, I'am happy with the current layout. Then we'll preserve the current layout. Thanks, - Jon -- You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/dblinq?hl=en.
