ASP.Net Remote Dev (Is this correct?)

[Chris]

The situation:

We have a remote web server (Server A), where we run our ASP.Net
application. There are 3 developers, each working on their pieces of the
application and updating Server A periodically.

Ideal situation:

Developers use the .Net Studio IDE to remotely connect to Server A and open
project files. As changes are made to files in each IDE, updates are
automatically propogated to Server A.

I read the MS article below, and it is my understanding that all we need to
do is:

1. Install .Net Server components on Server A (IIS is already there)
2. Install Frontpage Server Extensions (required?)
3. Add developer logins to "VS Developers" group on server for
authentication

Is this all I need to do?
Will this configuration interfere with existing applications running on
Server A?

MS Article on Remote Server Configuration for .Net: http://tinyurl.com/25jrn

TIA,
Chris

[bruce barker]

one limitation that makes using a shared development server impractical is
only one debugging session is allowed per asp.net server. this means your
developers will have to take turns debugging the app.

you are better off doing local development, and updateing the shared server.

-- bruce (sqlwork.com)

"Chris" <re**********************@hotmail.com> wrote in message
news:u4**************@TK2MSFTNGP10.phx.gbl...

The situation:

We have a remote web server (Server A), where we run our ASP.Net
application. There are 3 developers, each working on their pieces of the
application and updating Server A periodically.

Ideal situation:

Developers use the .Net Studio IDE to remotely connect to Server A and open project files. As changes are made to files in each IDE, updates are
automatically propogated to Server A.

I read the MS article below, and it is my understanding that all we need to do is:

1. Install .Net Server components on Server A (IIS is already there)
2. Install Frontpage Server Extensions (required?)
3. Add developer logins to "VS Developers" group on server for
authentication

Is this all I need to do?
Will this configuration interfere with existing applications running on
Server A?

MS Article on Remote Server Configuration for .Net: http://tinyurl.com/25jrn
TIA,
Chris

[Chris]

Thanks for the input.

One issue we have with that, is that one of the developers already has an
existing solution configured locally with the same. So my assumption was,
configuring another solution with the same name locally will get messy (we
have an existing web product which is getting repurposed).

Any ideas how to get around this so that a seperate instance of the solution
can be configured locally, even though it has the same name?

Thanks,
Chris

one limitation that makes using a shared development server impractical is
only one debugging session is allowed per asp.net server. this means your
developers will have to take turns debugging the app.

you are better off doing local development, and updateing the shared server.
-- bruce (sqlwork.com)

"Chris" <re**********************@hotmail.com> wrote in message
news:u4**************@TK2MSFTNGP10.phx.gbl...

The situation:

We have a remote web server (Server A), where we run our ASP.Net
application. There are 3 developers, each working on their pieces of the application and updating Server A periodically.

Ideal situation:

Developers use the .Net Studio IDE to remotely connect to Server A and

open

project files. As changes are made to files in each IDE, updates are
automatically propogated to Server A.

I read the MS article below, and it is my understanding that all we need

to

do is:

1. Install .Net Server components on Server A (IIS is already there)
2. Install Frontpage Server Extensions (required?)
3. Add developer logins to "VS Developers" group on server for
authentication

Is this all I need to do?
Will this configuration interfere with existing applications running on
Server A?

MS Article on Remote Server Configuration for .Net:

http://tinyurl.com/25jrn

TIA,
Chris