CODEWITHSUNDEEP
asp.net-mvcasp.net-mvc-3entity-frameworkvisual-studio-2012ef-code-first
test-in-prod
test-in-prod

Reputation: 498

EntityFramework.SqlServer not deployed in web publish

Noticed this odd thing going on, perhaps it's a bug but I might be missing something myself.

Suppose you have a solution with two projects: one is a MVC3 project, another is a class library for data access (Entity Framework model classes, data context and such).

The class library references EntityFramework (EF6) and EntityFramework.SqlServer libraries.

And the MVC project references this class library DAL. The DAL library may be used by some other code outside of the application, hence to decouple it from the web project.

Anyway, it appears that upon publishing the MVC3 project, the process misses copying the EntityFramework.SqlServer assembly to the publish/bin directory. However, it does publish base EntityFramework dll along with other libraries and the class library itself.

Is there a way to get the publisher to publish the required SqlServer driver as well?

Upvotes: 7

Views: 6177

Answers (3)

nimish jain
nimish jain

Reputation: 141

Add entity framework package in your package file of your project

Upvotes: 1

RredCat
RredCat

Reputation: 5431

I had the same situation. I installed EF to my web project via NuGet (I still don't use it there, just referenced to libraries) and it solve my issue.

Moreover, I can't reproduce this situation for other solution - I created new web project and referenced new lib - but deployment works.

Upvotes: 4

test-in-prod
test-in-prod

Reputation: 498

Alright, so after some additional Google-fu it appears that a workaround is to create some reference to that missing assembly, even if the code is unused.

.NET MVC 3 Deployment package missing references

And the workaround I used is add simple test line in the constructor of the data context:

bool instanceExists = System.Data.Entity.SqlServer.SqlProviderServices.Instance != null;

Upvotes: 16

Related Questions