RE: development environment architecture for ASP.NET development team

From: Cowboy (Gregory A. Beamer) - MVP (NoSpamMgbworld_at_comcast.netNoSpamM)
Date: 09/27/04 

Date: Mon, 27 Sep 2004 06:33:03 -0700

The preferred method is to develop locally and use some form of source
control (in most cases SourceSafe). When a developer is ready to push
something to a test server, he gets latest and ensures a build can compile.
It is then pushed up and tested.

NOTE: This was also true in the ASP world. 

---
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"Akhlaq Khan" wrote:
> hi,
> we have been working on web based applications built in ASP for quite
> sometime now, but now we are moving to ASP.net. we have decided to use
> ASP.NET for developing new modules in our current projects (built in ASP).
> So, the applications will be composed of both ASP and ASP.NET pages
> simultaneously. Since, ASP is a scripting language, it was easier for us to
> put all the source code on a single web server, add the web to visual
> soursafe using FP extentions in IIS, connect to the web applications from
> development workstations using visual interdev and start checking files
> in/out without any problem. the developers would test the effects of their
> changes right on the web server by hitting refresh or F5. Everything takes
> place on the web server, except code modification.
> 
> now, since we are moving from a scripting language to a "compiled" language
> (ASP.NET), that means the application would need to be "built" on
> development workstations before being deployed on server (check in), since i
> cannot expect my developers to build the application on server after every
> single change they make on their own machine, coz they will keep switching
> between machines forever. Moreover, i want the developers to be able to
> "debug" their appliactions rigth on other workstations (i found out that
> debugging is nearly impossible if application is placed on server, just like
> it was in ASP 3.0).
> 
> My question is:
> 
> 1. What are the standard/recommended architectures for setting up
> development environments for ASP.NET applications ?
> 2. Which one should i use if i want to use a).visual sourcesafe for version
> management. b) debugging capability for all developers on their own machines
> rather than server, c) easier maintenance/no or least code synchronization
> hassle.
> 
> desparately waiting for response ...
> 
> thanks,
> 
> akhlaq khan.
> 
> 
>

Relevant Pages

  • Re: Maintaining ASP.NET Sites
    ... more and more websites to get from everything else and into .Net. ... All you small developers, forget ... Everyone that tried a large migration from VB 6 or ASP ... Windows Server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • development environment architecture for ASP.NET development team
    ... ASP.NET for developing new modules in our current projects. ... the applications will be composed of both ASP and ASP.NET pages ... changes right on the web server by hitting refresh or F5. ... cannot expect my developers to build the application on server after every ...
    (microsoft.public.dotnet.framework.aspnet)
  • development environment architecture for ASP.NET development team
    ... ASP.NET for developing new modules in our current projects. ... the applications will be composed of both ASP and ASP.NET pages ... changes right on the web server by hitting refresh or F5. ... cannot expect my developers to build the application on server after every ...
    (microsoft.public.dotnet.general)
  • Re: development environment architecture for ASP.NET development team
    ... > we have been working on web based applications built in ASP for quite ... > ASP.NET for developing new modules in our current projects. ... > changes right on the web server by hitting refresh or F5. ... > cannot expect my developers to build the application on server after every ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: development environment architecture for ASP.NET development team
    ... > we have been working on web based applications built in ASP for quite ... > ASP.NET for developing new modules in our current projects. ... > changes right on the web server by hitting refresh or F5. ... > cannot expect my developers to build the application on server after every ...
    (microsoft.public.dotnet.general)
Loading