[Proposal] It should be possible to manually create SqlException

[ashmind]

SqlException create methods are currently internal.
I would like some kind of create method to be public.

Rationale

Unit tests. There are various scenarios in which SqlException is handled differently than other kinds of exceptions, and being able to test those scenarios without actual database would be useful.

Related StackOverflow thread, How to throw a SqlException when needed for mocking and unit testing?, has 53 upvotes.

Potential API

class SqlException {
    // ...
    public SqlException(
        string message,
        SqlErrorCollection errorCollection,
        Guid clientConnectionId = Guid.Empty,
        Exception innerException = null
    )  { ... }
}

class SqlErrorCollection {
    // ...
    public SqlErrorCollection()  { ... }
    public SqlErrorCollection(params SqlError[] errors)  { ... }
}

class SqlError {
    // ...
    public SqlError(
        int infoNumber,
        byte errorState,
        byte errorClass,
        string server,
        string errorMessage,
        string procedure,
        int lineNumber
    ) { ... }
}

Open Questions

Is there a better way to expose SqlError that would allow easier future extensibility?
Some kind of SqlErrorBuilder?

[divega]

As recently announced in the .NET Blog, focus on new SqlClient features an improvements is moving to the new Microsoft.Data.SqlClient package. For this reason, we are moving this issue to the new repo at https://github.com/dotnet/SqlClient. We will still use https://github.com/dotnet/corefx to track issues on other providers like System.Data.Odbc and System.Data.OleDB, and general ADO.NET and .NET data access issues.