Developing and backing up w/ .net
|
Original Message
|
Name: xhermit
Date: November 2, 2006 at 10:32:42 Pacific
Subject: Developing and backing up w/ .netOS: XPCPU/Ram: 1.5Ghz 512Model/Manufacturer: Dell |
Comment: Here at work we have a shared drive where we should be using to develop on. That way if your HD crashes you won't lose anything (and it HAS crashed... only been here for 5 months). The problem is I'm developing in asp.net and its wanting to store everything in c:/inetpub/wwwroot. This is not accessible on the shared drive, so I'm kinda stuck developing locally. Is there a way to develop locally, and have visual studio automatically back up to a shared drive? And wouldn't compiling be significantly slower on a shared drive? I'm open to different ideas. Thanks.
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: SN
Date: November 5, 2006 at 13:32:02 Pacific
|
Reply: (edit)The typical way to do this is via source control solutions like visual source safe, CVS, subversion, or visual studio team edition. Most have options of copying files to a particular directory (usually the dev, staging, or QA environment) when they are checked in. You definitely wouldn't want to do it the way you've described for windows forms development, but for ASP.NET development you could probably get away with it by setting your project up as a web project. Just be prepared to have more difficulty debugging and setting stuff up... Good luck, -SN
Report Offensive Follow Up For Removal
|
Use following form to reply to current message: