Is Kigg MVC application DRY? Can we tweak the Repository
问题 I was recently taking a look at the Kazi Manzur Kigg MVC implementation (Kazi rocks) and noticed some code that seemed to defeat the DRY/SOC principle. I'd love to have everyone's thoughts on a possible refactor to separate concerns. Kigg implements both an Add and Remove method on each repository class ( Note : BaseRepository has virtual methods than can be overloaded by each concrete implementation.) The implementations for the Kigg.Repository.LinqToSql.CategoryRepository and the Kigg