asp.net - Using EF and other Dapper ORM in same project - drawbacks -
i start new project , have little dillema. app require asp identity security , dapper orm. plan use default asp web app template identity use entity framework , business data access use dapper. means use dapper identity tables (like username user).
another approach change identity use dapper think not skilled enough , bad project later.
so drawbacks architecting app this?
there no drawbacks. orms tools. allowed use more 1 tool - pick appropriate tools each job. if building house wouldn't try use 1 hammer hammer-related jobs, or 1 screwdriver screw related jobs.
just keep isolation between them - ef models don't play nicely other tools.
Comments
Post a Comment