Home/ Questions/Q 7820245
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-02T07:13:26+00:00

I’ve read a lot of discussions about web site vs web applications in asp.net

  • 0

I’ve read a lot of discussions about web site vs web applications in asp.net

The way we work in my team (10 programmers), we use the project type “web site”, and for our dev environment, we just copy the source code (aspx + .cs) to the server. This way, all the programmers can be doing changes at the same time.. and the server does the build dynamically. …..(for the prod environment, they build the application)

Now, I’m starting a new project, and I decided to use web application (the main reason was the web config transform option).. I soon realized that (as far as I know) it forces you to do a build/publish of the web app to the server with every change… which is not a big problem if I’m the only one working on this project…

But, now I’m wondering, what’s going to happen if more programmers needs to work on this new project at the same time?

Any advise or similar situation?

EDIT

we’re using Visual Source Safe… but only for keeping track of the older versions (not for builds)… I’m familiar with Subversion… but.. unfortunately, I don’t take the decision on what we should use.. and I don’t think they’re willing to change

Thanks everyone for your answers…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Anytime I hear the, this isn’t a big problem as long as. . . . immediately tells me, that I should assume that it will be a problem. In short, go with what you know. If you are familiar with using the ASP.NET website, then I would use that. Your development practices are already focused around handling that.

    This is the same model that I used when doing classic ASP when I first started programming at a company. This model works, although I would strongly suggest getting source control too. That being said, here is what I would do long term:

    1. Source control
    2. Develop locally
    3. Get a continous build process going (cruise control is a free one).
    4. Have one person push everyone’s changes to the development server, once everyone agrees that all the changes are compatible with each other. (normally this is done by making sure the build server can compile everything).
    • 0