-
Notifications
You must be signed in to change notification settings - Fork 545
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
Designer file casing issue #2105
Comments
This issue has been closed because EF6 is no longer being actively developed. We are instead focusing on stability of the codebase, which means we will only make changes to address security issues. See the repo README for more information. |
I understand. Is it a no-no or if a PR comes in it gets a little fixup? I spent about 10 minutes trying to figure it out, so just wondering if it's worth for me to invest more time into this or not. |
We're very unlikely to accept a PR for this. |
@ajcvickers cool cool. I need to support an .NetFramework application with it. Say I make my data-layer EFCore6.0, I could not use it from a .NetFramework assembly right, so I would have to use an EFCore version that supports .NetStandard and they are all EOL anyway right ? |
Correct. |
When using package manager console to add a manual migration, it creates a .Designer file but in the project file it is referenced as .designer (lower case d). This is totally fine on windows, but on ubuntu build runners it fails as the filesystem is case-sensitive.
EF version: 6.4.4
Database provider: Microsoft SQL
Target framework: .NetFramework 4.7.2
Operating system: Ubuntu or other linux variants for this specific issue
IDE: Visual Studio 2022 community edition
The text was updated successfully, but these errors were encountered: