3 ms·

So you got to the third bullet point on the first page, forgot the first two, stopped reading and decided to comment?

by cup-of-tea 9y ago

fsloth 9y ago
The charitable way to put that would have been "I don't see how the features you listed are related to to the first two bullet points". I might have misunderstood some technical nuance in the article but I could honestly use the exactly same statements as in the first two bullet points to describe my workflow with VS. This is not with Git though, so that might complexify the process. Maybe someone who is working with Git repos using a Visual Studio integrated tool can comment on this detail.
- loup-vaillant 9y ago
  VS lets you save a sandbox per branch? May I ask since when? (The most recent version I have used was 2012).
  - fsloth 9y ago
    In my work I use VS with TFS as the source control. Each branch is in a separate directory, and one can store explicit change sets at any point in time as "shelve sets" without actually committing them into the repository. So there are the two hierarchy levels to experimentation - one can create a new parallel branch on the fly, or do experimentation on top of a branch using shelve sets. That's not explicitly a sandbox, but provides for most cases where one needs to experiment / have distinct development lines / put away random experiments etc. So, uh, depending where you need a sandbox the features may or may not exist.
    - sobani 9y ago
      On the other hand, in Git there is no difference between a branch, a check-in, a shelve set and a code review (which is also a shelve set). How nice would it be if you could just compile and run the code review yourself, reject it, and then immediately continue with your own work? Or even better, just run both the code review and latest at the same time and see the difference, not just read it.

3 ms·

So you got to the third bullet point on the first page, forgot the first two, stopped reading and decided to comment?

by cup-of-tea 9y ago

So you got to the third bullet point on the first page, forgot the first two, stopped reading and decided to comment?

fsloth 9y ago
The charitable way to put that would have been "I don't see how the features you listed are related to to the first two bullet points". I might have misunderstood some technical nuance in the article but I could honestly use the exactly same statements as in the first two bullet points to describe my workflow with VS. This is not with Git though, so that might complexify the process. Maybe someone who is working with Git repos using a Visual Studio integrated tool can comment on this detail.
- loup-vaillant 9y ago
  VS lets you save a sandbox per branch? May I ask since when? (The most recent version I have used was 2012).
  - fsloth 9y ago
    In my work I use VS with TFS as the source control. Each branch is in a separate directory, and one can store explicit change sets at any point in time as "shelve sets" without actually committing them into the repository. So there are the two hierarchy levels to experimentation - one can create a new parallel branch on the fly, or do experimentation on top of a branch using shelve sets. That's not explicitly a sandbox, but provides for most cases where one needs to experiment / have distinct development lines / put away random experiments etc. So, uh, depending where you need a sandbox the features may or may not exist.
    - sobani 9y ago
      On the other hand, in Git there is no difference between a branch, a check-in, a shelve set and a code review (which is also a shelve set). How nice would it be if you could just compile and run the code review yourself, reject it, and then immediately continue with your own work? Or even better, just run both the code review and latest at the same time and see the difference, not just read it.