Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
2 posts • Page 1 of 1
When Entity Developer code gens it puts the connection string into the generated class rather than into a configuration file and it doesn't put the res://*/ in front of the csdl, msl, and ssdl files so that when trying to use it (say from a Console app accessing the model in a data access layer dll) it can't find the files. I can manually add the res://*/ in and that will work until the model gets code generated and then my changes get blown away - this makes for a lot of rework updating those files or writing manual code to create the context. It is such a hassle that it reduces the usability of Entity Developer especially on an ongoing basis with existing models.
Last edited by HintonBR on Tue 15 Feb 2011 11:55, edited 1 time in total.