This happen when I try to use Migration in PMC. This is the only project I have in my solution and I have installed everything. Can someone help me with this, please?
The version of EntityFramework Core I'm using it's too high. After switching back to 2.2.0, it work fine.
Related
As soon as I've solved one issue with IBM.EntityFrameworkCore, another one has arose. Everything is soooo hard and painful with DB2 and their .NET team...
The problem: I have several EntityFrameworkCore - based projects in the same VS solution, for example MyDb2EfModel, MyMsSqlEfModel, and MyNpgsqlEfModel. (It's kind of a complex data-integration scenario.) On top of that I have a CLI project which references all the three and performs actual data ops. When the CLI project references only MyDb2EfModel project - IBM.EntityFrameworkCore works as expected. But as soon as I add references to the remaining two projects - it simply stops working and throws some misleading exception. The exception happens because overridden DbContext.OnConfiguring and DbContext.OnModelCreating methods aren't called anymore. When there's only one reference (MyDb2EfModel) the methods get called as expected, and everything works. But with all three library projects referenced - they aren't called anymore.
Let's also note that the mentioned methods get called on DbContext instances from MyMsSqlEfModel and MyNpgsqlEfModel libraries. The only one that stops working is MyDb2EfModel (which is based on IBM.EntityFrameworkCore).
Thumbs down for IBM and their .NET team! It's ridiculous how these guys are making things be 100 times more complicated then with any other DB.
The question is obvious: Does anyone has any experience in a similar scenario, and hopefully any suggestion how to resolve the issue?
Thanks!
I've found the reason. It turned out that it's about Microsoft.EntityFrameworkCore version. Currently available version of IBM.EntityFrameworkCore is 1.1.1.101 (.NET Standard 1.6), and it uses Microsoft.EntityFrameworkCore version 1.1.1 or 1.1.2. It cannot be used with Microsoft.EntityFrameworkCore version 2.0.0 (.NET Standard 2.0) - it throws the exception I was getting.
In the other two libraries I've used Npgsql.EntityFrameworkCore.PostgreSQL version 2.0.0 and Microsoft.EntityFrameworkCore.SqlServer version 2.0.0, both depending on Microsoft.EntityFrameworkCore version 2.0.0 (all in .NET Standard 2.0).
So when I referenced only MyDb2EfModel in my CLI project everything was working because only Microsoft.EntityFrameworkCore version 1.1.2 is referenced and used. But as soon as I add reference to another projects CLI ends up with dependencies on both Microsoft.EntityFrameworkCore version 1.1.2 and 2.0.0 versions, and the newer (2.0.0) is loaded and used. And IBM.EntityFrameworkCore was failing because it cannot use it.
How to solve? Either wait for IBM.EntityFrameworkCore for .NET Standard 2.0, or downgrade other references to ensure that Microsoft.EntityFrameworkCore version 2.0.0 isn't used anywhere (which will cause other headaches).
So although it's not about a bug in IBM.EntityFrameworkCore, IBM DB2 .NET team is still to blame for not having .NET Standard 2.0 at least preview published, although .NET Standard 2.0 is available for almost a year now, recently reaching its "release" version. And there are more things to blame IBM DB2 .NET team for (unrelated to this particular issue).
I've written a program that uses Code First with LocalDB to store data. After using Click Once to deploy, the application doesn't create the LocalDB in production. I've tried all of the Database Initializers, and the app just errors out saying that no tables actually exist.
I'm assuming that there is something simple that I'm missing, but all the articles I find seem to refer to using SQL Express.
Edit
May be related to EF 6.1.1. I've tried downgrading to 5 and it appears to be working, but I'm not done testing yet.
Downgrading EF from 6.1.1 to 5.0.0 has resolved this issue. I can only assume that this is a bug in 6.1.1.
How to go about upgrading moodle without all coursefiles going to the legacy folders?
I have tried re mapping files and creating links in the course area to the files that worked, but i am wondering if their any other way of going about it? Possibly upgrading further to 2.3+ could fix this issue?
Yes it is possible to upgrade moodle version from 1.9 to 2.2.
Please go through following url
http://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2
Can any one please tell me which version of drools-guvnor is more stabled than latest ?
I am currently using 5.3.0 , every time it is getting corrupted .I thought it was a war problem .
please give me some inputs on this .
I'm using 5.5.0.Final version and it works well.
As this is a tool that changes a lot, I'd like to use the 6 version as soon as possible. But at this moment, with 5.5.0 I can do all that I need.
Best regards, Jesús.
Before updating phpunit everything was ok, function assertRedirectTo() worked as it should, but after updating it shows this error:
Declaration of Zend_Test_PHPUnit_Constraint_Redirect::evaluate() should be compatible with that of PHPUnit_Framework_Constraint::evaluate()
Can anybody explain what exactly happened?
Yes, I ran into this problem too two days ago. But on the unfortunetly Zend Framework 1.x is not going to support PHPunit 3.6 or higher :-(
So the best thing is that you go back to 3.5 which is the latest version Zend Framework supports.
Check this:
http://zendframework.com/issues/browse/ZF-11871
Here you can read they will proberly make ZF2 supporting 3.6:
http://zend-framework-community.634137.n4.nabble.com/Running-the-zend-unit-tests-with-the-phpunit-3-6-PHP-CodeCoverage-Filter-getInstance-problem-td4023996.html