![]() ![]() config files are pretty universal across configurations and can stay stable, the most common problem are connection string differences amongst users. Config File Connection Strings under Source Control There are workarounds described in this StackOverflow Question, but they're not built-in and require some extra effort as well. config transformations on their own can't solve that problem easily. If you have test projects or re-use components in other types of applications like services or desktop apps. config transformations that can be applied that can mitigate some of this pain, but this only solves the problem for Web projects. In Web projects in Visual Studio there are. config file differences in general are problematic under source control. The problem is that on most developer machines there are differences in how connection strings - and even more specifically the server name - are referenced to access a database. Such a small thing, but I see that as a stumbling block for many projects starting up under source control especially for new developers. ![]() One basic question that I see time and time again with source control is how to manage connection strings stored in. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |