VSO (Visual Studio Online) m loving it
-
I'm a big fan of VSO. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Me too - although I found the build-deploy thing for Azure to be a bit cryptic...
-
Me too - although I found the build-deploy thing for Azure to be a bit cryptic...
To be honest, I only use it for version control and work item tracking. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
TFS is a PITA, as every other source control system is. Plan your actions, and hardly anyone needs to merge classes anymore. Seriously: Git is good, TFS is good, and they both suck equally.
I will never again mention that Dalek Dave was the poster of the One Millionth Lounge Post, nor that it was complete drivel.
"Plan your actions, and hardly anyone needs to merge classes anymore." 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. Not using any source control system, THAT's a PITA :)
-
"Plan your actions, and hardly anyone needs to merge classes anymore." 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. Not using any source control system, THAT's a PITA :)
AlexCode wrote:
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 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 ;)
We all have biased views :) The other things (build, load testing etc) are not SCM specific features.
-
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?
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.
-
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.
-
We all have biased views :) The other things (build, load testing etc) are not SCM specific features.
-
Valery Possoz wrote:
my company has moved to TFS online
That is great, even I am thinking of suggesting this in my company, it's just so simple. But I am not sure how will they fill about pushing the source onto cloud :(.
We at VSO appreciate this. And thanks for all those sexy, proprietary projects we'd never have got to see normally. No really! We will appreciate your input!:suss:
-
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?
-
To be honest, I only use it for version control and work item tracking. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Ravi Bhavnani wrote:
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.)
-
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've not used VSO yet, but I have been reading up on it and I am very intrigued. I wish I had more time to try it out.
-
I've not used VSO yet, but I have been reading up on it and I am very intrigued. I wish I had more time to try it out.
-
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.
-
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.
I plan to as soon as I get the chance. I have been using VS Ultimate 2013 for the past few months, and I am really excited about 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