Last post Sep 04, 2008 08:52 PM by mydreams
Sep 04, 2008 02:24 PM|davey_b|LINK
We have a ASP.NET project that's going to be worked on by a number of developers. Right now it's being developed via remote desktop conection to the server and using VS 2008. We're wanting a better solution and I'd like to run this by you guys to make sure
this plan makes sense:
1. Have VS on each developers machine with IIS installed
2. Create a virtual directory to the IIS server to copy the files to the local machine
3. With a SCM tool check files out and check them back onto the server
Does this make sense? Thanks!
Sep 04, 2008 03:59 PM|cv_vikram|LINK
Friend, if you have budget, you can better go for either sourcegearvault or sourceoffsite for configuration management.
They will cost around 250 bucks and they are very fast over network and internet. It has the server and client setup. Server software has to be installed into the server machine and
have the source.ini of of VSS to map and a similar client software in each developer machine.
It is basically a wrapper tool for VSS.
Sep 04, 2008 04:08 PM|davey_b|LINK
Thanks for the reply, we are looking into a few SCM systems and will check this one out as well.
I'm trying to understand the relationship between the local developers machine and the server the application will be accessed on, IOW, how to develop asp.net projects locally and then copy them to the server. I don't know if the SCM tools change that configuration
Sep 04, 2008 04:11 PM|shados|LINK
How you work is that everyone runs the application locally, either through the Visual Studio built in web server, or with local IIS, as you want it. Same deal with the database ideally, though opinion vary on that.
Then all of the code is managed by the source management system, and then you have a build server (can be the same machine, whatever). Something like CruiseControl.NET can be used for that, Team Foundation Server has one, you can use a simple NAnt script,
its up to you. You simply need something that can be invoked by someone in charge, that will pull the latest version of the source, and deploy it on a staging or production server. This can be done periodically.
Sep 04, 2008 05:21 PM|davey_b|LINK
Thanks for your reply. If I'm understanding you correctly we can write/test code on our machines and then publish to the server. I think we may be using visual source safe for the SCM, I'm thinking we'll be able to check out files from the server and create
a local copy and then check back in to copy to the server.
Thanks again for your help.
Sep 04, 2008 08:52 PM|mydreams|LINK
It it good.