EF code first using specific project on solution with ignoring migrations

102 Views Asked by At

I have a solution and it has many projects. My solution look like below:

MySolution

  • WinService1
  • WinService2
  • WebUI
  • Entities
  • DataAccessLayer
  • BusinessLogic

My Winservice1 and WinService2 projects used DAL. My problem is here. If somebody change entity and update database for WebUI project, I need to update my Windows services on the remote. But I don't want to update because their entities are specific and if they will change, this mean I have to update.

My question on here. Could I use a db-first database? Or is it possible to ignore (not check) migrations on specific projects? What's the best practices?

0

There are 0 best solutions below