problems with connection string generation in app.config

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Post Reply
nstraub
Posts: 2
Joined: Fri 11 Nov 2011 18:25

problems with connection string generation in app.config

Post by nstraub » Fri 11 Nov 2011 18:52

Hi!

whenever I generate the class files using the entityobject template, a connection string is added to my app.config called whatever I call it repeated as many times as I generate the model (so if I generate the model for the third time and my cs is called entities, I'll have 3 cs's in my config, called entities, entities.entities, and entities.entities.entities). I'm using version 4.1.64. could someone help me fix this?

Thanks!

Shalex
Devart Team
Posts: 8036
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Mon 14 Nov 2011 15:22

nstraub wrote:whenever I generate the class files using the entityobject template, a connection string is added to my app.config called whatever I call it repeated as many times as I generate the model
Both Entity Developer (the Devart Entity Model template, *.edml) and Entity Data Model Wizard (the ADO.NET Entity Data Model template, *.edmx) give an opportunity to set the name of connection string to store it in app.config on the step when you are specifying the connection string parameters. Please set the name of connection string manually.

If this doesn't help, specify the exact steps we should follow to reproduce the problem.

nstraub
Posts: 2
Joined: Fri 11 Nov 2011 18:25

Post by nstraub » Mon 14 Nov 2011 15:54

steps:

- create a new dbfirst edml with connection name set to "entidades"
- build the edml twice.
- in app.config two entries will appear, one called "entidades" and the other one "entidades.entidades"

if done a third time a new cn will appear called "entidades.entidades.entidades".

if you need more info tell me.

Thanks!

Shalex
Devart Team
Posts: 8036
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Tue 15 Nov 2011 16:39

We cannot reproduce the problem at the moment.

1. Please upgrade to the latest (4.1.71) version of Entity Developer. Does the problem persist with 4.1.71 as well?
2. Tell us your edition of Entity Developer.
3.
nstraub wrote:- build the edml twice.
What do you mean saying "build"? Is it pressing the "Save" button of Visual Studio, when the model designer is active, or generating another model with the same name of connection string or what?

Post Reply