Last post May 14, 2013 02:28 PM by SushmaRamakrishna
May 13, 2013 04:10 PM|SushmaRamakrishna|LINK
In my app.config I have a connectionstrings section that when I use the configSource directive to point to another file for the connectionstring, I cannot undertaken ANY modifications to the edm model. When the designer appears, in the properties the ConnectionString
is blank. This is ONLY restored by placing the connectionstring entry BACK into the app.config and then removing the configSource.
I am having to place the connectionstring into a separate file simply because of my clients requirement for encryption of the authentication elements of the connectionstring.
Have found that unless the connectionstring exists in the App.Config, the Entity Framework designer does not populate the connectstring entry in the properties block. Any attempt to refresh from database results in a new connectionstring build request being
I was using an external config file, that was duly addressed by the configSource directive. This was working fine for general development but it seems that the Entity Framework Designer, can not function unless the connectionstring is actually in the app.config.
If an external config file is used, the connectstring is blank in the designer.
(We had a requirement to encrypt a number of athentication items in the connectionstring, this is working well with the exception that access to the Entity Framework designer isn't possible.
We considered using the "web.config separation via location attribute" to control the web.config access from different developers.
Here is a good web article mentioned:
#Split web.config for Different Environments
We could separate the sensitive config info into a separate config file and only those privileged users can access it (read and write access).
The Entity Framework designer does not populate the connectionstring entry in the properties block.
Please could somebody give suggestions.
Thank you ,
May 14, 2013 10:54 AM|DarrellNorton|LINK
I faced a similar issue because I was generating the connection string dynamically at runtime.
In the dropdown if you save a dev or test connection string in App.Config/web.config it will work - then just remove them before deployment using an XML transform or MSBuild or whatever you use to deploy.
Or each time you can create a new connection, update the EDM, and then not save the connection string.
May 14, 2013 02:28 PM|SushmaRamakrishna|LINK
Thank you very much for you suggestions.
Since you have mentioned work around for DEv environment. Does that mean that this issue exists only locally and not when deployed?