-
Notifications
You must be signed in to change notification settings - Fork 684
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
Failed executing DbCommand - ORDER BY items must appear in the select list if SELECT DISTINCT is specified. #771
Comments
I think I had the same problem here and solved it by compiling it myself #642 (comment) |
@OndrejValenta Thanks for the tip but it didn't work. I now forked the project and updated it to .net7 and fixed the ef core stuff. Will push it soon to github, but azure storage must be fixed first. I'll contact the maintainer if he will continue to update the project or I can take it under the umbrella of my company. Edit: |
. I'll contact the maintainer if he will continue to update the project or I can take it under the umbrella of my company. wanted to do the same thing, there are forks that fixed other problems but this repo seems stucked |
Probably @loic-sharma will allow you as administrator into this project. |
Let me know if/when you get your answer from @loic-sharma, pls.. |
@OndrejValenta @CPlusPlus17 I think this repo is dead and @loic-sharma abonded it. You can clearly see that he is almost every day active on GitHub. I tried to reach him on Twitter too, but no response of him. |
I would say, you are correct,
Are you really taking over of this project? |
I have the feeling that if the project is continued by others/oss then another name would be better to prevent confusion with this NuGet name/path. Because this project here seems to run (dead) all side along with the new one. |
The maintainer left the nuget team due to burnout and needed distance to this project; passing on maintenance privileges is however proposed: #780 |
This is true, but on the other hand he said, that we should fork BaGet under a new name (when we want to see progress). |
Describe the bug
Enable mirroring for nuget and click refresh in IDE to get newest packages lead to this log in baget.
The text was updated successfully, but these errors were encountered: