Re: development environment architecture for ASP.NET development team
From: Kevin Spencer (kspencer_at_takempis.com)
Date: 09/27/04
- Next message: Ken Dopierala Jr.: "Re: development environment architecture for ASP.NET development team"
- Previous message: Ken Dopierala Jr.: "Re: Login Page Problem; Click Events not fired"
- In reply to: Akhlaq Khan: "development environment architecture for ASP.NET development team"
- Next in thread: Ken Dopierala Jr.: "Re: development environment architecture for ASP.NET development team"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 27 Sep 2004 09:14:42 -0400
Hi Akhlaq,
I can't tell you the "best" way, but I can tell you how we do it. We have XP
Pro workstations for our developers, each with IIS running on it. We use
Visual SourceSafe as well. We check the ASP.Net projects into SourceSafe,
and work from local copies. This prevents one developer from working on
something another developer has checked out.
When you use VSS with ASP.Net, the project files are created in the web
directory on the client machine. The project file itself can be anywhere. We
keep the project files in our documents folders, along with our non-web app
project folders. When another developer needs a copy, he opens the project
from VSS, copying the files into a new web app which VS.Net sets up.
Just make sure that only Projects, not solutions are kept in VSS, and you
should be fine.
-- HTH, Kevin Spencer .Net Developer Microsoft MVP I get paid good money to solve puzzles for a living "Akhlaq Khan" <auzkhan@newsgroup.nospam> wrote in message news:O6SZA5GpEHA.592@TK2MSFTNGP11.phx.gbl... > 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. > >
- Next message: Ken Dopierala Jr.: "Re: development environment architecture for ASP.NET development team"
- Previous message: Ken Dopierala Jr.: "Re: Login Page Problem; Click Events not fired"
- In reply to: Akhlaq Khan: "development environment architecture for ASP.NET development team"
- Next in thread: Ken Dopierala Jr.: "Re: development environment architecture for ASP.NET development team"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
