New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Cannot bind argument to parameter 'Path' because it is an empty string" when running Add-Migration #52
Comments
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: info@zzzprojects.com if you need to keep the source private Best Regards, Jonathan |
Hello @schuettecarsten, Since our last conversation, we haven't heard from you. Could you provide a full example of this issue on our email: info@zzzprojects.com Looking forward to hearing from you, Jon |
Hello,
If you use default "entityFramework" section - change code above accordingly |
Thank @rmaenk for the answer ;) It might be exactly the solution. |
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, |
This did not help, unfortunately. |
I sent you an email some days ago... |
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 |
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. |
When I run “Add-Migration” from the package manager console, I get:
Please note that in my project, I have moved the DbContext and the Migrations into a separate assembly “CMT.DataAccess” and the Model into an assembly “CMT.DataAccess.Model”. This worked fine for EF6. To migrate from EF6 to EFClassic, I removed all EntityFramework packages and installed the EFClassic packages as described in the documentation.
The text was updated successfully, but these errors were encountered: