We have a solution which consists of two projects - a console application project and a web application project. Each of these has an identical in schema, but differently named
When faced with this problem in the past, I've always created a third, shared library that contains the entity model - that way you know there's not going to be a name conflict, if you decide to add a new table/column/method to the model you only need to do so once, etc, etc.