Re: development environment architecture for ASP.NET development team

From: Ken Dopierala Jr. (kdopierala2_at_wi.rr.com)
Date: 09/27/04


Date: Mon, 27 Sep 2004 08:25:15 -0500

Hi,

This will link you to a presentation, almost 2 hours long, that will show
you how to set everything up in a few different ways:

http://support.microsoft.com/default.aspx?scid=kb;en-us;328845

Good luck! Ken.

-- 
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight
"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.
>
>


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: Developing ASP.NET w/out IIS or Admin Rights
    ... You might be able to collect remote debug information from your ... ASP.NET web applications using a local version of IIS 5.0 and SQL Server ... How can a team of 8 developers test & debug applications ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Server 2003 with Visual Studio.NET
    ... Would stand-alone Windows applications developed using a server OS as ... developers throughout the years have argued that it is more "convienient" to ... A QA test must be an install on a virgin Win ...
    (microsoft.public.windows.server.general)