Entity connection name is out of standards

Question

Entity connection name is out of standards

Navigation

#1 by (1 votes)

1

Whenever I change the database, I need to delete edmx and re-create it since update from database is not updating. So far so good. Whatever happens now he has created a connection with the totally non-standard name. It looks like this:

win-mdsk429aa7b.V99_Web.dbo

Before it was just V99_WebEntities. This name appears when I give a New Conection and it appears in the compbo where I have the connections. How do I delete this connection to return to normal, as it was before? If I do not change the connection, I will have to change my whole system, out of the question.

When I delete edmx, I also delete the line from my web.config for edmx deleted.

c# entity-framework

asked by anonymous 27.05.2014 / 15:19

1 answer

How to change validation text according to each type of validation in the Initial Date field Remote Access Mysql Amazon Server

score 1 · Accepted Answer

I need to understand these things well. Was solved. I have a solution with several projects, being one of them, a Web Service. As in the current moment I have been working on the Web Service, it is like my main project and has its components opened in the IDE, such as the .svc and the interface. Whenever I create a new connection, it gives me this error. What did I do. I closed the WS, opened my main project, set it up for the start up project, and when I created a new edmx, it worked as before. I do not know why but it was WS.

I rushed. He gave the mistake again. He had not. But I had done something wrong. I changed and when I went to do it again, gave the error already quoted.

I have found that the name it mounts is the name of the machine where the bank is. And it was not working on IIS, because of this: When I published, I had to publish web.config because of a change I made (I never sent web.config, but it was necessary this time). But for me, web.config was pointing an ip where the bank is. But this IP is masked and read only from the outside in. So, with web.config typing this IP it does not recognize (from inside), then it does not find the bank because the IP does not exist for it. I went to localhost and it worked. Now, all set.