VSO (Visual Studio Online) m loving it
-
BobJanova wrote:
TFS's source control is one of the worst I've used
No offence but I do not see the reason to believe that Or, I just have less experience than you do.
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.
-
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.
BobJanova wrote:
No merging back of branches
Maybe I misunderstood what you meant by this, but I've merged back branches with no problems. :confused: /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
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.
Oh man, you do know more than I do, clearly its because I do not have any experience with Git and SVN, I will definitely give them a little time and learn about them. But hey, I'm using TFS from last 2 years and I did not face any issue. So may be it is not that bad after all. (Well of-course it depends on one's use.).
-
BobJanova wrote:
No merging back of branches
Maybe I misunderstood what you meant by this, but I've merged back branches with no problems. :confused: /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
I am one of the early adopter and I like it so much for my personal use, I can easily share my code with my friends and even work with them, please try it out it's awesome and powerful.
Me too. I've been using it before it was known as Visual Studio Online and have been using TFS since 2007. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
I'd never trust confidential code to a cloud service. If you think TFS is a better source control system than Git then ... :confused:. TFS's source control is one of the worst I've used.
BobJanova wrote:
I'd never trust confidential code to a cloud service.
Me either. I just can't stop seeing the cloud as a big backdoor to my source code that I have neither visibility nor control of. Worse, I can't get rid of the feeling of risk that I could find myself locked out of my own source by the cloud provider.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
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?
My one gripe about VSO w/ Git is that they don't support some of the Build niceties that you get if you use TFVC. Most notably, checking drops back in to SCC. Makes it hard to fab up chained builds and separate out your projects well. Means I have had to resort to checking in binaries that could otherwise be pulled from a Drops folder if they'd bring that functionality to the Git area. Nonetheless, I have migrated *all* my projects over to VSO Git from Bitbucket & elsewhere, so I totally agree!:thumbsup:
-
My one gripe about VSO w/ Git is that they don't support some of the Build niceties that you get if you use TFVC. Most notably, checking drops back in to SCC. Makes it hard to fab up chained builds and separate out your projects well. Means I have had to resort to checking in binaries that could otherwise be pulled from a Drops folder if they'd bring that functionality to the Git area. Nonetheless, I have migrated *all* my projects over to VSO Git from Bitbucket & elsewhere, so I totally agree!:thumbsup:
BC3Tech wrote:
migrated *all* my projects over to VSO Git from Bitbucket & elsewhere,
Wow, you have a nice article there. One more thing, I have to admit, I do not have any experience with Git, But I do like to invest some time in learning it and gaining some experience. It seems a lot of people are giving more credit to GIT than to TFS.
-
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?
So what do you guys do when the internet is not working? I work on sites which are phone dead zones and where there is no internet access. Guess I'll never know what it is like in a work environment. What happens if you have super-slow broadband or an uppy-downy connection - how do you use that time productively?
-
BC3Tech wrote:
migrated *all* my projects over to VSO Git from Bitbucket & elsewhere,
Wow, you have a nice article there. One more thing, I have to admit, I do not have any experience with Git, But I do like to invest some time in learning it and gaining some experience. It seems a lot of people are giving more credit to GIT than to TFS.
Thanks for the compliment on the post, hopefully you found it useful. Honestly I didn't have any Git experience either. Having an IDE built around it (Visual Studio) that does all the command-line stuff for you is very helpful. I have a friend that works at MS and the word is that internally all projects are built on Git and TFVC receives no more funding. To me that means it's going away - hence my reason for "jumping in".
-
So what do you guys do when the internet is not working? I work on sites which are phone dead zones and where there is no internet access. Guess I'll never know what it is like in a work environment. What happens if you have super-slow broadband or an uppy-downy connection - how do you use that time productively?
-
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?
VSO is pretty nice, but only for personal projects, I won't trust Microsoft my work projects source code, that's why I have my own TFS server somewhere in the cloud... ;P
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
VSO is pretty nice, but only for personal projects, I won't trust Microsoft my work projects source code, that's why I have my own TFS server somewhere in the cloud... ;P
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
I can not agree more, Closed Source in cloud is a horrible idea : I think. not just in Microsoft's cloud but in any cloud.
It have its benefits, as long as you have a backup somewhere else.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...