Hi
To say that I have been driven to distraction by this would be something of an understatement.
I have an application built upon the entity framework (winforms, .net 4.5). It was designed as database first and the connection string is in the app.config file (which of course isn't exposed in a winforms app when deployed). To get around the almost
inevitable mis match with connection strings I have utilised the nugget package for the Microsoft connection dialog and when my app first runs on an end users machine it will prompt them to create a new connection string with said dialog. On my development
machine(s) this all works well and the application can be run against many different databases.
So now of course we come to deployment. Initially end users will probably want to run the application on a single computer so it makes sense for them to use sql express. So to test this I have taken two new machines and placed clean inst ...
Go to the complete details ...