|
Belgarath posted:The Sourcesafe integration with Visual Studio handles all that at the moment (when you edit the file, it checks it out and makes it writeable, vice-versa on check-in), although as you say, it is a concern of mine that once I break that link, things could go a little haywire. I'm not sure if Visual Studio will make a file writeable that it doesn't think is under version control. You might want to setup 2 IDE projects for this, 1 hooked into VSS and 1 where you'll manage things on your own. You can use the VSS one to do small changes and checkin/checkout via the IDE. When you want to get git involved, do a manual checkout on all of the files involved via the standalone VSS client, create your git repositories, then use that 2nd IDE project. When you're done, push the completed files from your git repo back to your VSS working dir and checking via the VSS client. That said, I think this is a pretty crazy idea. You're probably going to run into issues when you start moving and renaming files, 2 things which VSS is notoriously bad at. You also need the foreknowledge of which files you want to checkout from VSS before you start working on your feature. Once the scope expands, you may find you need a file that someone else is already working on.
|
#
¿
Sep 12, 2009 23:37
|
|
|
|
| # ¿ May 7, 2024 07:37 |
|