Tag Info

New answers tagged

1

Your application code and your EDMX should be portable, i.e. you should not need to change either of them when moving between Environments. That means no database (or schema) names "hard-coded" in there or, if there are, you should be able to replace them using nothing more complex than a global Search-and-Replace. Anything "cleverer" and all bets are off. ...


1

YMMV, but in our environment, we prefer any test code automatically to be rebuild after a change to library on which the test code depends was made. Having to switch between configurations first makes it easier to forget the rebuild. And don't you run into trouble when you try to debug through the test applications, and step from the test application's code ...



Top 50 recent answers are included