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
Problem If having Empty connection string #131
Comments
I don't follow what is the culprit of the error. With that I can review the change and merge, and release. |
culprit was not checking dictionary.containsKey for various key in connection string. will learn about this pull request in a bit of free time |
Hi @bruno-garcia , |
Good point. I'll make a release this weekend. |
Thanks bruno. Do add a small line here whenever it is done |
I pushed another preview out, please let me know how things work so we can roll out a stable one: |
Looks like This preview have null check resolved via new extension method? |
Sorry but I'm not sure I understood the question. Could you please clarify?
I updated |
I was saying that if some configuration of connection string missing i hope no exception raise in the current preview release. |
I am creating Connection string dynamically. when i am leaving my default connection string to empty my application get into infinite loop.
I am using .net core 3.1. On investigation i found the reason is due to Uri.cs
Ideal fix should be like in the attached class
Uri.zip
The text was updated successfully, but these errors were encountered: