Hm. Ok, to clarify, for anybody else who may have been just as confused at my description, let me offer the following example, directly from the class library:
First and foremost, the library was to be a fluent mapper for Linq2Sql, so I have the following:
Second, I wanted to bundle in a base repository so I wouldn’t have to keep adding it to my actuall apps, so I added in the following:
Third, I needed an interface that specilized repositories could use to aide in overcoming concurrency issues, so I added:
Next, I decided to add some other common things from my standard list of things I do in my mvc apps, so I added the following:
Because I validate in services, I also added:
Lastly, I added some extension method classes and a controller factory for use with StructureMap.
Right now, as you can see, everything is one namespace. I rather like the idea of being able to simply add “using FluentEngine” and have access to everything I need. On the other hand, something like the following might be order…
Or should I rip out things that aren’t actually part of the fluent engine itself, and put them into a separate library?
Is that more clear? Anyway, I’d like a few more comments before I decide how to wrap this up.