The function CreateIfNotExists refers to the static ConnectionString. However, it is possible to call the DataContext constructor with a *different* connection string ... which then appears to be ignored.
I appreciate that most of the time the connection strings as templated by the toolbox are what is required but it is possible that alternative strings may be required. Indeed, it may be appropriate to build ConnectionString and ConnectionStringReadOnly from a filename (which could be passed) rather than assuming that anyone calling the constructor will have passed one of the two static connection strings.
Thanks for a great toolbox! Saved me a lot of headaches.
Philip
I appreciate that most of the time the connection strings as templated by the toolbox are what is required but it is possible that alternative strings may be required. Indeed, it may be appropriate to build ConnectionString and ConnectionStringReadOnly from a filename (which could be passed) rather than assuming that anyone calling the constructor will have passed one of the two static connection strings.
Thanks for a great toolbox! Saved me a lot of headaches.
Philip