Hi. Recently we've updated some (non-ASP.NET Boilerplate) packages like EntityFramework and more (around 20 packages that visual studio asked to update). The problem is that we now get lots of weird exceptions like "unknown method" from Boilerplate's dll's. We can't really know where the problems are exactly because they come from some Boilerplate dll's we cannot see. Does it mean that if I'm working with ASP.NET Boilerplate, I am not allowed to update packages that ASP.NET Boilerplate framework relies on ? Why isn't there a mechanism which tells that Boilerplate dll's are depended on some other specific dll versions (like entity framework v4.0) so this update would be restricted and the project wouldn't be destroyed? (Boostrap, For example, has this line written in their nugget : Dependencies : jQuery (>= 1.9.1 && < 3.0.0) ) As for now we are working on downgrading those nuget packages (but it's like impossible cause we don't know the previous versions). Anyway, the project is very unstable now (I'm getting these errors only on runtime!). That do you suggest? (We are using the latest ASP.NET Boilerplate versions and nuggests)
Thanks.
2 Answer(s)
-
0
One more question: Is there a reason that the latest version of Asp.Net Boilerplate contains some very old nuget packages? For example, why are you using log4net v1.2.0? (There are plenty of versions above it and the latest one is v2.0.5)
-
0
Because Castle Logging Facility only supports log4net 1.2.0. They are working on that. When it's released, we will upgrade.
