http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660" * Make it simpler to treat each project independently * Make it easier to deal with the management of each project (dependencies, build scripts) " Although it's certainly more work for you, I'm glad to hear this. http://ayende.com/4155/the-complexity-of-unity#comment12http://ayende.com/4155/the-complexity-of-unity#comment12Sun, 30 Aug 2009 18:05:32 GMT@Patrick Smacchia I own a licence for NDepend and suggest you send a complimentary license to Oren as he may use and write about the product. I this would be a great marketing move on your part. http://ayende.com/4155/the-complexity-of-unity#comment11http://ayende.com/4155/the-complexity-of-unity#comment11Sun, 30 Aug 2009 16:47:15 GMTolivierey, Right now, do nothing, I am still playing around with everything. Consider this just my way of thinking out load. I'll make proper announcements about everything when I am done. http://ayende.com/4155/the-complexity-of-unity#comment10http://ayende.com/4155/the-complexity-of-unity#comment10Sun, 30 Aug 2009 16:06:35 GMTOren, sorry, but i didn't get it. i have a dependancy to rhino.security trunk in my current project and thinking about updating it. what should i do? should i change to the git repository (you're talking about splitting things up) or should i stay with the svn trunk? ... the question is, witch one do i need, to get the newest pieces from (like the svn trunk) , ... , maybe you can clarify your plans for the future, i think there are some other out there, who also have dependencies. which tools do you use for git instead of tortoise/visual svn? thx http://ayende.com/4155/the-complexity-of-unity#comment9http://ayende.com/4155/the-complexity-of-unity#comment9Sun, 30 Aug 2009 15:32:01 GMTOren, does this mean [rhino-tools.svn.sourceforge.net/.../rhino-tools](https://rhino-tools.svn.sourceforge.net/svnroot/rhino-tools) is deprecated? http://ayende.com/4155/the-complexity-of-unity#comment8http://ayende.com/4155/the-complexity-of-unity#comment8Sun, 30 Aug 2009 15:18:22 GMTPatrick, I am not sure that I am following you here. The issue is not so much the indirect dependencies, it is taking a dependency that either change the way you work or bring a lot of additional dependencies with it http://ayende.com/4155/the-complexity-of-unity#comment7http://ayende.com/4155/the-complexity-of-unity#comment7Sun, 30 Aug 2009 11:42:23 GMTOliviery, You can check it out here: [http://github.com/ayende](http://github.com/ayende) http://ayende.com/4155/the-complexity-of-unity#comment6http://ayende.com/4155/the-complexity-of-unity#comment6Sun, 30 Aug 2009 11:40:58 GMT>For example, Rhino ETL using Rhino Commons, but then this creates a dependency between Rhino ETL and Castle Windsor, although Windsor isn't used in Rhino ETL Have you tried the indirect dependency mode that will pinpoint this sort of 'indirect' dependencies issue? http://ayende.com/4155/the-complexity-of-unity#comment5http://ayende.com/4155/the-complexity-of-unity#comment5Sun, 30 Aug 2009 11:40:25 GMTPatrick, I mean that it is easier to take a dependency on a project in the same repository, it make it easy to work with them together. The problem is that this creates ties between the projects. For example, Rhino ETL using Rhino Commons, but then this creates a dependency between Rhino ETL and Castle Windsor, although Windsor isn't used in Rhino ETL Rhino Security is an even worse example, it make so much use of the architecture in Rhino Commons that you can't make use of it at all without following the UoW pattern as laid out in RC http://ayende.com/4155/the-complexity-of-unity#comment4http://ayende.com/4155/the-complexity-of-unity#comment4Sun, 30 Aug 2009 11:07:11 GMTConsider Mercurial instead of Git. It's (pretty much) the same thing, only more "human friendly". Have a look and tell us your opinion. =) http://ayende.com/4155/the-complexity-of-unity#comment3http://ayende.com/4155/the-complexity-of-unity#comment3Sun, 30 Aug 2009 11:01:44 GMTwhere can we see its progress? if i click show log on the trunk, i see nothing http://ayende.com/4155/the-complexity-of-unity#comment2http://ayende.com/4155/the-complexity-of-unity#comment2Sun, 30 Aug 2009 10:18:41 GMT>I have been working on splitting the Rhino Tools projects to all its sub projects, so each of them is independent of all the others. I am not sure to understand but are you saying that managing dependencies to decrease how projects depends on each other is a good thing? Btw did you try NDepend for that? http://ayende.com/4155/the-complexity-of-unity#comment1http://ayende.com/4155/the-complexity-of-unity#comment1Sun, 30 Aug 2009 09:46:49 GMT