What steps will reproduce the problem? Just passing in a string value to SqliteConnection is fine, but I have a program that is passing around a ConnectionStringBuilder, and unless there is another option would like the SqliteConnectionStringBuilder to not be sealed.
-public sealed class SqliteConnectionStringBuilder : DbConnectionStringBuilder {
What is the expected output? What do you see instead? -public class SqliteConnectionStringBuilder : DbConnectionStringBuilder {
var connectionInfo = e.Data as ConnectionInfo; var connectionBuilder = connectionInfo.Builder as SqliteConnectionStringBuilder;
What version of the product are you using? On what operating system? 3.7.7.1
Please provide any additional information below.
Comment #1
Posted on Mar 14, 2015 by Grumpy OxNot sure why, but after a few builds it eventually allowed the sealed class to be used. So no need for changing it.
Status: New
Labels:
Type-Defect
Priority-Medium