I'm thinking the latest version of IsDisallowed.cs I pulled down still has a hard-coded connection string?
In Version 1.2 and later the connectionString is no longer subject to the restriction defined in this thread.
For best service when you require assistance:
I notice too that I have to edit the Settings.Settings file to get it to refresh and pull in my connectionstring from the app.config file (in the DataSource project).
I don't do a lot of strongly typed datasets, but I wonder is there a way to tweak this so it will pull automatically and not seem to hard-code this and require an edit?
Yeah, you're right.
I think I have an answer on how to put the connectionString in Application.config...
I just checked in a fix for the ConnectionString woes. The settings designer file and the functions project now point to ApplicationSettings.ConnectionString. I'm actually surprised that the Functions project works the way it does. You can't add a reference to System.Configuration from Visual Studio but you can if you edit the project file directly. Strange...???
Of course, this means that it works on my machine but won't elsewhere...
In Release 1.1 the ConnectionString for the Functions project is hardcoded, but as a temporary measure, there exists a check on startup to ensure the ConnectionString in Application.config is the same as the one in IsDisallowed.cs.