Who uses IDE-integrated source control?
-
Lazyness I guess. Start typing code, will checkout the file, you can always see the status of the file in the project window without changing programs. When closing the project, will auto check all files into VSS for safe keeping. Al
Thanks. :)
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
-
Naw... this way, people will see a gray post in The Lounge, and think "wow, he must have posted something interesting". By the time they figure it out, they'll already have read it... ;)
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
-
Quick poll, vote:
1 if you do 5 if you don't 3 if you don't use any source control, but like to click things
I haven't, ever since installing SoS a few years back, and realizing how much time i'd been wasting in Visual Studio trying to manage source control (or just waiting for VS to connect and update its little status icons...). I'm much, much more productive leaving all source files writeable, and waiting until check-in time to merge. But for those of you that do use it, what are your reasons for doing so?
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
Project policy that all code be in source control. I'm on-line therefore I am. JimmyRopes
-
Naw... this way, people will see a gray post in The Lounge, and think "wow, he must have posted something interesting". By the time they figure it out, they'll already have read it... ;)
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
-
Quick poll, vote:
1 if you do 5 if you don't 3 if you don't use any source control, but like to click things
I haven't, ever since installing SoS a few years back, and realizing how much time i'd been wasting in Visual Studio trying to manage source control (or just waiting for VS to connect and update its little status icons...). I'm much, much more productive leaving all source files writeable, and waiting until check-in time to merge. But for those of you that do use it, what are your reasons for doing so?
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
-
;)
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
-
Lazyness I guess. Start typing code, will checkout the file, you can always see the status of the file in the project window without changing programs. When closing the project, will auto check all files into VSS for safe keeping. Al
Albert Pascual wrote:
When closing the project, will auto check all files into VSS for safe keeping.
Doesn't that make the history of each file almost useless? Don't you get a new version every time you edit the file in a development session?
-
Albert Pascual wrote:
When closing the project, will auto check all files into VSS for safe keeping.
Doesn't that make the history of each file almost useless? Don't you get a new version every time you edit the file in a development session?
You don't need to use that feature, The editor asks you if you want to check the files in. You can say no or cancel and then check in with comments ( also the admin can force comments). I normally add a label before a build and I check out history by label. Cheers Al
-
Naw... this way, people will see a gray post in The Lounge, and think "wow, he must have posted something interesting". By the time they figure it out, they'll already have read it... ;)
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
Shog9 wrote:
people will see a gray post in The Lounge, and think "wow, he must have posted something interesting"
So true! I always check out the grey coloured posts just to see what someone said that upsets someone else.:->
"You're obviously a superstar." - Christian Graus about me - 12 Feb '03 "Obviously ??? You're definitely a superstar!!!" - mYkel - 21 Jun '04 "There's not enough blatant self-congratulatory backslapping in the world today..." - HumblePie - 21 Jun '05 Within you lies the power for good - Use it!
-
Shog9 wrote:
people will see a gray post in The Lounge, and think "wow, he must have posted something interesting"
So true! I always check out the grey coloured posts just to see what someone said that upsets someone else.:->
"You're obviously a superstar." - Christian Graus about me - 12 Feb '03 "Obviously ??? You're definitely a superstar!!!" - mYkel - 21 Jun '04 "There's not enough blatant self-congratulatory backslapping in the world today..." - HumblePie - 21 Jun '05 Within you lies the power for good - Use it!
-
I use AnkhSVN to add SVN integration to VS2005 and it has worked very well for me. I never took the time to learn the full set of SVN commands so using Tortise and AnkhSVN have worked out great for me.
-
Quick poll, vote:
1 if you do 5 if you don't 3 if you don't use any source control, but like to click things
I haven't, ever since installing SoS a few years back, and realizing how much time i'd been wasting in Visual Studio trying to manage source control (or just waiting for VS to connect and update its little status icons...). I'm much, much more productive leaving all source files writeable, and waiting until check-in time to merge. But for those of you that do use it, what are your reasons for doing so?
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
What's SoS? I googled it and the closest I could get was source gear vault. Why it over subversion?
I only read CP for the articles. Code-frog System Architects, Inc.
-
What's SoS? I googled it and the closest I could get was source gear vault. Why it over subversion?
I only read CP for the articles. Code-frog System Architects, Inc.
Source Off-Site - a replacement for SourceSafe from the makers of Source Gear Vault. Makes using SS remotely bearable. And also makes using SS from home bearable. ;P
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
-
Quick poll, vote:
1 if you do 5 if you don't 3 if you don't use any source control, but like to click things
I haven't, ever since installing SoS a few years back, and realizing how much time i'd been wasting in Visual Studio trying to manage source control (or just waiting for VS to connect and update its little status icons...). I'm much, much more productive leaving all source files writeable, and waiting until check-in time to merge. But for those of you that do use it, what are your reasons for doing so?
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
I hate IDE integration, even went so far as to disable it in the registry
HKCU\Software\Microsoft\Devstudio\6.0\Source Control\Disabled = 1(yes, we still use VC6 here...)
I have only one superstition. I touch all the bases when I hit a home run. - Babe Ruth
-
Quick poll, vote:
1 if you do 5 if you don't 3 if you don't use any source control, but like to click things
I haven't, ever since installing SoS a few years back, and realizing how much time i'd been wasting in Visual Studio trying to manage source control (or just waiting for VS to connect and update its little status icons...). I'm much, much more productive leaving all source files writeable, and waiting until check-in time to merge. But for those of you that do use it, what are your reasons for doing so?
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
I have always been trying for the past 2-3 years of my professional life to use SourceSafe from within IDE but I have never been able to do it successfully without any problems. But then again, it comes down to which language are u working in. I mostly (99%) work in Visual C++ , and I have found out that VSS support for VC in VS.NET is particularly sucking. It is better for C# and VB.NET though. In the end, what I end up doing is that I get the whole code from sourcesafe and make it writable. And after doing my changes or whatever, I do a diff. of the whole folder and check in the individual things with comments. "Writing specifications is like writing a novel. Writing code is like writing poetry."
-
Quick poll, vote:
1 if you do 5 if you don't 3 if you don't use any source control, but like to click things
I haven't, ever since installing SoS a few years back, and realizing how much time i'd been wasting in Visual Studio trying to manage source control (or just waiting for VS to connect and update its little status icons...). I'm much, much more productive leaving all source files writeable, and waiting until check-in time to merge. But for those of you that do use it, what are your reasons for doing so?
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
Shog9 wrote:
But for those of you that do use it, what are your reasons for doing so?
Shared access. For a small team, I have more trust in the VSS way of "I checked that out, don't touch it", than the CVS "take it, we merge it" way. One thing that is not so nice: "Using Source Control for the automatic backup" sometimes conflicts with "only check in working code". I'd love a "user-specific pin", that is, when I pin a certain revision, a normal "GET" will retrieve the pinned version for all others but me, but I still have the full liberty of modifications.
Some of us walk the memory lane, others plummet into a rabbit hole
Tree in C# || Fold With Us! || sighist -
Quick poll, vote:
1 if you do 5 if you don't 3 if you don't use any source control, but like to click things
I haven't, ever since installing SoS a few years back, and realizing how much time i'd been wasting in Visual Studio trying to manage source control (or just waiting for VS to connect and update its little status icons...). I'm much, much more productive leaving all source files writeable, and waiting until check-in time to merge. But for those of you that do use it, what are your reasons for doing so?
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
I hate IDE-integrated source control. The IDEs don't offer all the features of the standalone client anyway, so you have to know how to use that (this is true even of SourceSafe). I recall Eric Sink (of SourceGear) saying how the MSSCC API was horrible to implement and only dealt in terms of what SourceSafe is capable of anyway (no changeset/transactional checkin support, for example). I'm like you: I prefer to make all my changes locally to writeable files, then commit once I'm done. I find that there actually aren't often clashes on source files, so merging is rarely required - if you find that you are merging a lot, you should reconsider the physical structure of your project. It doesn't help that some of the IDEs modify some of the files (resource scripts, project files in VC6 and eVC) in a create-new-delete-old-and-rename fashion, which Vault (2.0.6 at least, we need to upgrade) doesn't detect, and so doesn't add to the changeset. My colleagues however are happy with the IDE integration and relying on the read-only flags to force the IDE to make an exclusive checkout on beginning an edit. My experience is that this often isn't reliable. Stability. What an interesting concept. -- Chris Maunder
-
Quick poll, vote:
1 if you do 5 if you don't 3 if you don't use any source control, but like to click things
I haven't, ever since installing SoS a few years back, and realizing how much time i'd been wasting in Visual Studio trying to manage source control (or just waiting for VS to connect and update its little status icons...). I'm much, much more productive leaving all source files writeable, and waiting until check-in time to merge. But for those of you that do use it, what are your reasons for doing so?
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
I don't mind integrated SCC for checkouts (in fact, it's rather convenient!) but for checking in I always use the SCC IDE directly as I prefer to independently check the files as they are checked in, customising the check-in comment for each as appropriate. It really bugs me when I see people do a mass check in of all of their files without bothering to do that, and unfortunately integrated SCC makes it all too easy. Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
-
Shog9 wrote:
But for those of you that do use it, what are your reasons for doing so?
Shared access. For a small team, I have more trust in the VSS way of "I checked that out, don't touch it", than the CVS "take it, we merge it" way. One thing that is not so nice: "Using Source Control for the automatic backup" sometimes conflicts with "only check in working code". I'd love a "user-specific pin", that is, when I pin a certain revision, a normal "GET" will retrieve the pinned version for all others but me, but I still have the full liberty of modifications.
Some of us walk the memory lane, others plummet into a rabbit hole
Tree in C# || Fold With Us! || sighistpeterchen wrote:
One thing that is not so nice: "Using Source Control for the automatic backup" sometimes conflicts with "only check in working code". I'd love a "user-specific pin", that is, when I pin a certain revision, a normal "GET" will retrieve the pinned version for all others but me, but I still have the full liberty of modifications.
Team Foundation Server has a feature called "Shelving" which seems to offer this functionality: Overview of Branching, Merging, and Shelving[^] It's a pity you can't get TFS version control without a VSTS subscription, or we'd jump on it! Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
-
Quick poll, vote:
1 if you do 5 if you don't 3 if you don't use any source control, but like to click things
I haven't, ever since installing SoS a few years back, and realizing how much time i'd been wasting in Visual Studio trying to manage source control (or just waiting for VS to connect and update its little status icons...). I'm much, much more productive leaving all source files writeable, and waiting until check-in time to merge. But for those of you that do use it, what are your reasons for doing so?
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
Still using VSS with VC version 6. It's integration support for check-in/check-out works great. I can add new files/classes to projects with no problems. And from time to time, it's merge facility seems to work, too. What I like/use the most though, is that a stand alone machine used exclusively for building the release versions has .BAT files that automate all the building, versioning and labelling through the command line. The one thing I've stayed completely away from though, is I've never run any of the admin utilities on the sourcesafe database. Perhaps I'm lucky, but it's database of files have never failed me. Chris Meech I am Canadian. [heard in a local bar] When I want privacy, I'll close the bathroom door. [Stan Shannon] BAD DAY FOR: Friendly competition, as Ford Motor Co. declared the employee parking lot at its truck plant in Dearborn, Mich., off limits to vehicles built by rival companies. Workers have to drive a Ford to work, or park across the street. [CNNMoney.com] Nice sig! [Tim Deveaux on Matt Newman's sig with a quote from me] -- modified at 9:13 Wednesday 15th February, 2006