"Cannot bind argument to parameter 'Path' because it is an empty string" when running Add-Migration about entityframework-classic HOT 9 OPEN

Hello @schuettecarsten ,

Could you provide your project to make sure we try to debug it with your current setup?

So we will be sure that when the fix will be released, it will work with your model.

You can send it to: [email protected] if you need to keep the source private

Best Regards,

Jonathan

 
Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations • Dapper Plus
 
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

from entityframework-classic.

Hello @schuettecarsten,

Since our last conversation, we haven't heard from you.

Could you provide a full example of this issue on our email: [email protected]

Looking forward to hearing from you,

Jon

from entityframework-classic.

Hello,
I am not sure about your configuration, but just in case, try to specify ConfigSection for migrations like this:

    internal sealed class Configuration : DbMigrationsConfiguration<YourDBContext> {
        static Configuration() {
            Z.EntityFramework.Classic.EntityFrameworkManager.ConfigSectionName = "entityFrameworkClassic";
        }

If you use default "entityFramework" section - change code above accordingly
Regards,
Roman

from entityframework-classic.

Thank @rmaenk for the answer ;)

It might be exactly the solution.

from entityframework-classic.

I will give it a try, thank you.

Meanwhile I moved back to EF6 with EF+ because there were too many side effects. So, testing this might take some time. I will close this issue,

from entityframework-classic.

internal sealed class Configuration : DbMigrationsConfiguration<YourDBContext> {
    static Configuration() {
        Z.EntityFramework.Classic.EntityFrameworkManager.ConfigSectionName = "entityFrameworkClassic";
    }

This did not help, unfortunately.

from entityframework-classic.

Hello @schuettecarsten ,

Could you provide your project to make sure we try to debug it with your current setup?

So we will be sure that when the fix will be released, it will work with your model.

You can send it to: [email protected] if you need to keep the source private

I sent you an email some days ago...

from entityframework-classic.

Hello @schuettecarsten ,

We are sorry for the delay in our answer.

We have received your email and we are currently looking at the issue.

We will contact you via email.

Best regards,

Jon

from entityframework-classic.

Thank you for the project,

We can successfully reproduce it. We will need to review the part of the migration under the .NET Standard.

However, it doesn't look to be a quick job as we will need to sync our repo with the official EF versions.

We currently need first to complete our code re-write for EF Core 5 which is coming soon.

from entityframework-classic.