Add sugar to UseSqlServer and similar to help building connection strings.

Open
#15,642 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
backend, databases

Research direction

Start by reviewing the APIs contributed in PR #13463 and the UseSqlServer and similar provider entry points named in the issue. Compare the existing SqlConnectionStringBuilder experience with the proposed fluent-class and discrete-argument alternatives; done requires a decided user-experience direction before the 3.0 release.

Written by the indexing model from the issue text.

Description

area-dbcontext needs-design

This are new APIs we said we wanted to have and were contributed on https://github.com/aspnet/EntityFrameworkCore/pull/13463/.

I am creating this issue to make sure we remember reviewing the user experience before we ship it in 3.0.

Some impressions I have after playing with the API suggest that the experience suffers from the fact that SqlConnectionStringBuilder isn't fluent enough.

Possible alternatives could be to create our own fluent class, or create overloads of UseSqlServer (and other providers) that take discrete arguments such as database name and server name, and choose defaults for other arguments.

Dominant language
C#
Stars
14.8k
Forks
3.4k
Avg merge
2d 5h
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/efcore

All issues in dotnet/efcore

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.