Home/ Questions/Q 7808183
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-02T03:04:22+00:00

To start with some background, I am a member of a small team developing

  • 0

To start with some background, I am a member of a small team developing an ASP.NET application. In addition to us, there are 2 other teams working on it, all from different countries. Source code is hosted on a shared SVN server but there is no central testing environment. Each developer runs the app on their own machine and data services are set up per team.

Unfortunately our SVN workflow has some gaps in it: annoyances arise when there is time for an SVN update.

It is mainly because each developer and team have slightly different environments in terms of disk directory structure and configuration (both IIS and app itself). Hence conflicts in configuration files and elsewhere that in essence are not conflicts at all – for runtime configuration (XML) and in *.suo.

How should we handle this if our objective is to keep checkout, app setup and update as painless as possible?

One option would obviously be master copies. Another one establishing uniformity in developer environments and keeping it. But what about a third alternative?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    For IIS configuration there should be no argument – uniform environment across the build team.

    For app.config files and the like, I tend to keep them in a separate “cfg” directory in the root of the project and use pre-build events to copy in the relevant ones I need depending on the project and environment I’m working on.

    You could have a separate build task to copy in user-specific config into your output directory. Add a new directory in your root project called “user.config or something, and leave it empty. Then configure your project build to check this for entries and copy them to the output directory. This is easy to do, and then each dev can have their own config without affecting the master copies. Just make sure you have an ignore pattern on that folder so you don’t commit user-specific configuration. If you have svnadmin access to your source code repo, you could set a hook to prevent it from ever happening.

    Also set ignore patterns on your root directory (recursively) for .suo, .user, _Resharper or any other extensions you think are pertinent. There are some So questions already on exactly this topic:

    Best general SVN Ignore Pattern?

    • 0