Skip to content
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

Entity Framework raised Exceptions due to missing providerNames #9

Merged
merged 1 commit into from
Jul 23, 2015
Merged

Entity Framework raised Exceptions due to missing providerNames #9

merged 1 commit into from
Jul 23, 2015

Conversation

crunchie84
Copy link
Contributor

This commit fixes this by appending default providernames to connectionstrings configured in the Azure Portal. The defaults are as specified by the database providers themselves so we end up with a usable sane default situation.

Also included additional testcases to verify that the providernames are prefilled correctly

This commit fixes this by appending default providernames
to connectionstrings configured in the Azure Portal.

The defaults are as specified by the database providers
themselves so we end up with a usable sane default situation.
Restuta added a commit that referenced this pull request Jul 23, 2015
…zureportal-connectionstrings

Entity Framework raised Exceptions due to missing providerNames
@Restuta Restuta merged commit 3f1cef3 into Yegoroff:master Jul 23, 2015
@Restuta
Copy link
Collaborator

Restuta commented Jul 23, 2015

Thanks!

@crunchie84
Copy link
Contributor Author

😄

@michielpost
Copy link
Contributor

Can you make a new NuGet package with this fix? Thanks!

@Restuta
Copy link
Collaborator

Restuta commented Aug 8, 2015

@Yegoroff can you? what is the current process for NuGet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants