development process.... what is the best way ?

[Darren Clark]

Currently when developing a asp.net site...

I run the sql server on a remote server..

and the web files on my local so that i can debug without taking over the who iis on the development server.

my question is...

how does everyone else work? how can i fit some version control software in between so i can always go back to check old code?

[Steve C. Orr [MVP, MCSD]]

I run everything locally.
I use SourceSafe. Your SourceSafe database can be local or remote.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net
"Darren Clark" <dc******@hotmail.com> wrote in message news:%2****************@TK2MSFTNGP12.phx.gbl...

Currently when developing a asp.net site...

I run the sql server on a remote server..

and the web files on my local so that i can debug without taking over the who iis on the development server.

my question is...

how does everyone else work? how can i fit some version control software in between so i can always go back to check old code?

[Rick Spiewak]

I agree with Steve. Run everything locally for debug - use web.config to parameterize things like connection strings. Use VSS. Check in your solution whenever you have it working and are about to break it <g>.
"Steve C. Orr [MVP, MCSD]" <St***@Orr.net> wrote in message news:O6**************@TK2MSFTNGP12.phx.gbl...
I run everything locally.
I use SourceSafe. Your SourceSafe database can be local or remote.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net
"Darren Clark" <dc******@hotmail.com> wrote in message news:%2****************@TK2MSFTNGP12.phx.gbl...

Currently when developing a asp.net site...

I run the sql server on a remote server..

and the web files on my local so that i can debug without taking over the who iis on the development server.

my question is...

how does everyone else work? how can i fit some version control software in between so i can always go back to check old code?

[Darren Clark]

What about running the thing on the dev box... so remotely...

with source safe on that machine../.

then i have been told that i can configure iss to create new processes for each app in IIS?

so then i can debug one site witout taking the entire iis down?
"Rick Spiewak" <ri*********@mindspring.com> wrote in message news:Oa*************@TK2MSFTNGP10.phx.gbl...
I agree with Steve. Run everything locally for debug - use web.config to parameterize things like connection strings. Use VSS. Check in your solution whenever you have it working and are about to break it <g>.
"Steve C. Orr [MVP, MCSD]" <St***@Orr.net> wrote in message news:O6**************@TK2MSFTNGP12.phx.gbl...
I run everything locally.
I use SourceSafe. Your SourceSafe database can be local or remote.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net
"Darren Clark" <dc******@hotmail.com> wrote in message news:%2****************@TK2MSFTNGP12.phx.gbl...

Currently when developing a asp.net site...

I run the sql server on a remote server..

and the web files on my local so that i can debug without taking over the who iis on the development server.

my question is...

how does everyone else work? how can i fit some version control software in between so i can always go back to check old code?

[MR. UNDERHILL]

I'm working with a Team that it's actually in different countries, and we found that is very helpfull to have a Central Database and Local IIS. We use VSS in a central server and Source Off Site to connect to the VSS over the WAN

We have also all the store procedures and table scripts in source control, and we actually before do any modification to the database, we check-out the script, modify the script, run the script and check-in back the script, so we can get back in case of a mistake, and it's a good backup of our database in terms of logic

Good luck