Closed joseftw closed 1 year ago
You cannot mix version of EF and this plugin - you'll have to wait until an 8.0 version of this package is released. That will happen a bit later in the year.
Roger, thank you ❤️
@roji I think many of the consumers of this invaluable library are well aware of the inability to mix versions, however, I suggest you keep this issue open until a v8 or preview version is made available.
@miguellira how would keeping the issue open help?
@roji the error raised does not immediately indicate a version conflict. Novice developers will have to search closed issues to arrive at this thread.
I'd imagine as the .NET 8 release approaches, many developers will be testing their apps on the latest bits and will encounter this error more and more.
If you prefer to keep the issues list clean, maybe a note in the README?
I haven't seen closed issues being a problem - people who search for issues seem to check these as much as they do open ones, whereas people who don't really search (which is frequently the case unfortunately) wouldn't find an open issue either.
I get a couple of these issues with every release, and close them with the explanation as above, it hasn't been a big problem up to now.
@roji appreciate that 8.0 isn't supported, but I've submitted a PR that works against 7.0 and 8.0 after it stopped working in 8.0, thanks. #211
Hi @roji - I take your point but what is nice about keeping the issue open is that we can turn on notifications and get a ping when the issue is resolved. This issue is blocking us from testing EF Core 8 (and I totally get why this isn't your top priority) but it would be great if the issue was kept open so we'd know when it was resolved?
Can you update it to use it with RC1?
@mhosman as noted, this will happen a bit closer to the 8.0 release - I'm currently too busy with other things.
I've had this issue on RC1, RC2 now and it's not obvious what's going on. Did you guys fix this or am I doing something wrong still?
@DenisSikic nothing has changed, please read the above comments. You'll have to wait for an 8.0.0 release of EFCore.NamingConventions, which will happen in the next few weeks.
Thank you @roji , looking forward to it!
@DenisSikic nothing has changed, please read the above comments. You'll have to wait for an 8.0.0 release of EFCore.NamingConventions, which will happen in the next few weeks.
Hi @roji
I upgraded to .net 8.0.0 (non rc) today, and these issues went away with the naming conventions package being on 8.0.0-rc2.
However, I have a MAUI project in the same solution that doesn't use postgres, but uses Microsoft EFCore SQL Lite packages. They're all on 8.0.0 official release, but as soon as I touch the database I keep getting:
Value cannot be null. (Parameter 'source')
Couldn't find anything on the web that worked. Any ideas?!
@DenisSikic can you please open a new issue with a minimal repro for that? Ideally this would be a simple console program and not a MAUI project.
It went away with Microsoft nuget packages (non ef core related) coming out today, that weren't available yesterday. Just went away on its own. :S Thanks!
Thank you for your awesome work with all the different npsql packages.
Package versions:
I'm using the
UseSnakeCaseNamingConvention
method like this: (Full code here)When running my tests (trying to migrate the database), the following error occurs: (Full stacktrace)