The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I spend my time split roughly 60:40 between js & win32 c++
Two strings are approaching the TSA checkpoint at an airport, where the line of passengers is exceedingly long. To the annoyance of the passengers in line waiting to be security checked, the two strings are allowed to pass right on through the checkpoint, unchecked, ahead of all of the other passengers. When one of the passengers asked the TSA agent how this could have happened, the agent said:
Wait for it
"Sorry we don't search strings"
"... having only that moment finished a vigorous game of Wiff-Waff and eaten a tartiflet." - Henry Minute "...who gives a tinker's cuss?" - Dalek Dave "Let's face it, after Monday and Tuesday, even the calendar says WTF!" - gavindon It's plain that they do not yet know what true fear really is. - JSOP 2011
VSO (Visual Studio Online) it the best thing Microsoft ever done for me. I am now having all my projects stored online and to do that I no longer have to use messy (no offence) Git based source control systems. I can use my favorite TFS and have my code always accessible to me. Thank you Microsoft **Do you fill the same?
I have never had any experience with SVN, I've just used it pull code off of websites and nothing more, But feature like build, load testing, and integrated work management system that comes with VSO makes it a pro. even I'd prefer simple TFS-Express over anything else. ** This may be biased view
Really? Mate, I don't know the size of your team, the type of project or how you designed your app but merges are neither a problem nor the only/main advantage of a source control solution.
I was merely picking on the projects where 2 or 3 people work on the same file, and then they claim that "the SCS is BS because the merge is a PITA". Of course, not using any isn't great either - I work on a 5 people team, and TFS works kinda OK for us.
I will never again mention that Dalek Dave was the poster of the One Millionth Lounge Post, nor that it was complete drivel.
I only use it for version control and work item tracking.
@Ravi, You definitely should use it for you task management and build deployment, I'm sure you will save a lot of your time, and it also is very simple so you don't have to invest much time in learning it (I've never used VSO for it though.)
Completely agree, VSO is really cool, for my needs it's a no brainer! I use the free version for myself and at work my company has moved to TFS online. no server to maintain, no backup to deal with, no infrastructure. It's just easy.
If we're talking about just the source control part: - No virtualised branching or tagging (you have to actually copy the whole repository to the branch!) - No merging back of branches - Check in won't tell me if I need to do an update - Attempting to do 'Get latest' when there are merge issues gets the local copy in an inconsistent state unless you notice the entry in the message log (which is not the default view) telling you there are conflicts - Conflict resolution is bad, sometimes auto-merge loses changes - No local repository (SVN also doesn't have this, of course) - VS integration (right click Solution/Project) only sees files VS knows about, not support files in the same directories, making it easy to get in an inconsistent state
Then there's the issues with the build pipeline and half-arsed attempt at CI: - No chained or dependent builds - No ability to generate build artifacts and pass them to a later build - No way to have a build step that runs an external process (e.g. NAnt or batch scripts)
And the task management system in an agile environment: - Rigidly enforced difference between items in the task backlog and items that appear on the work board - Inability to multi-select or multi-drag on any of the web UI - Inability to start or end a sprint part way through a day - No understanding of story points, velocity etc
I've done previous work with SVN, JIRA and TeamCity, and everything is pretty straightforward. For the last few months I've been working with TFS (client mandated) and we've been fighting the tool at every step. It's possible to bodge something together which just about works regarding the build pipeline, but it took a couple of weeks of work on my part and it's still nowhere near as usable as TeamCity.
Last Visit: 31-Dec-99 19:00 Last Update: 21-Jan-17 18:24