1
I have an MVC project. At Solution are hanging some auxiliary projects. Well, it turns out that I’ve added a few references and when I start the project it gives me the error of saying that one project has a more up-to-date reference than the other. However, I put the two versions the same and continue. How do I solve this? It’s like this. A project called Infrastructure.Data, has the same version as System.Web.MVC(4.0.0.1). The Infrastructure project doesn’t really need this reference, but if I remove it, it gives me several "sticks", so I preferred to leave, but it keeps giving error. Down with the error:
Error 1 Assembly 'Operator.Infrastructure.Data, Version=1.0.0.0, Culture=neutral, Publickeytoken=null' uses 'System.Web.Mvc, Version=4.0.0.1, Culture=neutral, Publickeytoken=31bf3856ad364e35' which has a Higher version than referenced Assembly 'System.Web.Mvc, Version=4.0.0.0, Culture=neutral, Publickeytoken=31bf3856ad364e35'
c: Projects_mvc Operator.Infrastructure.Data bin Debug Operator.Infrastructure.Data.dll Operator.
What I find strange is that in trying to fix the problem, this came to me and it was all working, and I don’t know what’s going on:
Error 1 The type 'System.Data.Entity.Dbcontext' is defined in an Assembly that is not referenced. You must add a Reference to Assembly 'Entityframework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. C: Projects_mvc Operator.MVC Brandcontextfacade.Cs 17 18
Operator.
So it turns out that I added the same reference to both projects and I don’t know why is giving this version inconsistency.
– pnet
In reality everything was stuck in the Entity’s Assembly. I removed everything and reinstalled it and it solved. He would give a message, but the core of the problem was in Entity. By Nuget I updated everything and now it’s fine.
– pnet
It’s no problem see well, is that shocked versioning among the various other installed packages, but also reinforcing you do not need to have the
System.Web.Mvc
in all projects ... Well I’m just warning you ...– Cezar