Staging environment for two asp developers?

[jason]

What is the best way to allow a second developer access to existing html and
asp files in the office from a development point of view. At the moment, I
have been developing locally and then uploading my files to my web host but
I now need to create a usuable office environment which allows a second
developer to work my folder structures and files.

We do not have a big budget.

I am thinking of asking the company to buy a second hard drive loaded with
Office XP professional and use this to server files locally in a staging
environment before pushing the files to the remote web host.

Am I on the right track?
Many thanks
Jason

[Ray at]

Heh. Thanks Chris. At the moment, no. I almost posted twice to the SQL
programming group today, but both times, I had my "ah-ha" moment as I was
writing out my problem. Sometimes that's all it takes. I just have that in
my signature so that when I do post in the sql groups, some kind SQL-expert
soul may say to himself, "alright, fine, I'll help him out since he tries to
help out people in other places" I guess...

I spend half of my day in the asp groups and the other half just reading the
sql.programming group. And the third half of my day is spent working. ;]

Ray at work
"Chris Hohmann" <hohmannATyahoo DOTcom> wrote in message
news:eW******** ******@TK2MSFTN GP12.phx.gbl...

"Ray at <%=sLocation% >" <myfirstname at lane34 dot com> wrote in message
news:uX******** ******@TK2MSFTN GP12.phx.gbl...

--
Will trade ASP help for SQL Server help

Color me curious, but is there something specific in SQL Server you need
help with? I love to try, considering how often you appear on the answer
side of things.

-Chris

[jason]

Hey Ray,

Just some further clarification:

I am pitching this new server to our current administrator who is well
versed in mapped drives and network link ups etc.

But, obviously a new server running Win2k server would be operating
principablly via IIS to SERVER web files.

I am unsure how this scenario clashes/FITS/complements or unhinges the
network environment.

I mean, do we first install the new machine in our network and then make
sure everyone in the office is mapped to it or is the different scenario to
make sure that they are able to view web files like this:

http://newserver/test/homepage.asp

I realise it is a naive quesiton but networking is not my strong suite and I
just need to understand some of the key steps to getting it up and running -
not the entire tecnical process!

Much appreciated
Jason
"Ray at <%=sLocation% >" <myfirstname at lane34 dot com> wrote in message
news:eQ******** ******@TK2MSFTN GP10.phx.gbl...

<inline replies>

"jason" <ja***@catamara nco.com> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

Yeah - we don't have a test server. I am kind of reluctant to do a share as

it seems 'ineffecient' but I may be able to persuade company to buy a test server.

There wouldn't be anything inefficient about sharing a directory on your
machine. That's what the NT server service is there for. :]

I am I right in thinking all I really need is the latest harddrive Pentium III with enough memoery and Win XP PROFFESIONAL loaded which has IIS

built

in and then test sites locally using multiple site functionality found in ISS along the lines of:

http://local.mysite.com
http://local.mysite2.com

...which allows multiple domains pointing to various root folders in the
wwwroot of the newly acquired server machine...

You will not be able to setup multiple sites in XP Pro. You would need a
server operating system for this (NT Server, 2000 Server, 2003 Server).
With the desktop OSes, IIS only supports one single website. So, since
you'd need a server OS, add another $800 to your budget.

But, you should have a test server. Hopefully you can swing it. I mean,

if nothing else, is your DESKTOP workstation on the backup rotation? Probably not!

BTW, you're site's really nice looking. It makes me want to buy a
catamaran.

Ray at work