4 ms·

Visual Studio's naming scheme is pretty strange. They'll release this version in 2015 and the Visual Studio DLLs were previously on version 12. So it'd have ma

by Permit 12y ago

Visual Studio's naming scheme is pretty strange. They'll release this version in 2015 and the Visual Studio DLLs were previously on version 12. So it'd have made sense to name it Visual Studio 2015 or Visual Studio 13, but they opted for 14.

CurtHagenlocher 12y ago
The number 13 seems to get skipped for superstitious reasons.
- deleted 12y ago
  [deleted]
- TwoBit 12y ago
  If a software engineering company has superstitions then I wonder about their engineering capabilities.
  - KNoureen 12y ago
    Probably a management decision, not an engineer one.
  - abcd_f 12y ago
    Yeah. And don't get me started on all those construction and elevator companies that skip 4th and 13th floors. Brrr.
daigoba66 12y ago
See here: https://twitter.com/jongalloway/status/473912144761602048 https://twitter.com/jongalloway/status/473912144761602048
- jongalloway2 12y ago
  That's what I've been told. I am often wrong and / or misinformed.
- ethomson 12y ago
  Soma's blog states 'Visual Studio "14" will most likely be available sometime in 2015'.
ethomson 12y ago
14 is not the public (marketing) name, it's our internal version number. The currently shipping version, as you note, is version 12 (internally), but is called Visual Studio 2013 on the box. There is not necessarily a relationship between the version number that is used internally and the version number as described my marketing. I don't think we've made any public statements about "why 14", but I'm sure that you can draw your own conclusions as to why we jumped from 12 to 14 without a 13 in the middle. (ObDisclaimer: I work on the Visual Studio TFS team.)
- TheAnimus 12y ago
  I really like visual studio as an IDE, but I find myself really liking some of the things in 14. vNext, removing the cruft from my current stack, Rosyln at it's least simplifying the difference between my intelisense and actual compile. But as you are on the TFS team I feel you are a good person to ask, are there many improvements from a TFS source control perspective? It still feels 'clunky' if I want to commit and run a specific build it's laborious. Oh and lets not even ask why my visual studio online builds, with their paid azure account haven't built anything in the last 5 hours :( I do like the ecosystem, I like an IDE that lets me do everything in one place, that is extensible enough to ensure I can od everything I need there. But the current interactions, maybe tonights downtime has made me angry, are rather disappointing.
  - ethomson 12y ago
    From a version control perspective, we're investing heavily in Git right now, which brings a DVCS ecosystem into Team Foundation Server. This means that you can choose between using a checkout/edit/checkin model (TFVC "server workspaces"), a much more relaxed edit/merge/commit model (TFVC "local workspaces") or a DVCS (Git). I hope that wasn't too marketing speak-y. Anyway, sorry things feel clunky. I would definitely suggest moving from a server workspace to a local workspace if you haven't already and don't need some of the guarantees it makes about locking files for checkout and such. An edit/merge/commit system isn't nearly as chatty with the server and is much more pleasant to use on a daily basis.

by Permit 12y ago

CurtHagenlocher 12y ago

The number 13 seems to get skipped for superstitious reasons.

deleted 12y ago
[deleted]
TwoBit 12y ago
If a software engineering company has superstitions then I wonder about their engineering capabilities.
- KNoureen 12y ago
  Probably a management decision, not an engineer one.
- abcd_f 12y ago
  Yeah. And don't get me started on all those construction and elevator companies that skip 4th and 13th floors. Brrr.

daigoba66 12y ago

See here: https://twitter.com/jongalloway/status/473912144761602048 https://twitter.com/jongalloway/status/473912144761602048

jongalloway2 12y ago
That's what I've been told. I am often wrong and / or misinformed.
ethomson 12y ago
Soma's blog states 'Visual Studio "14" will most likely be available sometime in 2015'.

ethomson 12y ago

14 is not the public (marketing) name, it's our internal version number. The currently shipping version, as you note, is version 12 (internally), but is called Visual Studio 2013 on the box. There is not necessarily a relationship between the version number that is used internally and the version number as described my marketing. I don't think we've made any public statements about "why 14", but I'm sure that you can draw your own conclusions as to why we jumped from 12 to 14 without a 13 in the middle. (ObDisclaimer: I work on the Visual Studio TFS team.)

TheAnimus 12y ago
I really like visual studio as an IDE, but I find myself really liking some of the things in 14. vNext, removing the cruft from my current stack, Rosyln at it's least simplifying the difference between my intelisense and actual compile. But as you are on the TFS team I feel you are a good person to ask, are there many improvements from a TFS source control perspective? It still feels 'clunky' if I want to commit and run a specific build it's laborious. Oh and lets not even ask why my visual studio online builds, with their paid azure account haven't built anything in the last 5 hours :( I do like the ecosystem, I like an IDE that lets me do everything in one place, that is extensible enough to ensure I can od everything I need there. But the current interactions, maybe tonights downtime has made me angry, are rather disappointing.
- ethomson 12y ago
  From a version control perspective, we're investing heavily in Git right now, which brings a DVCS ecosystem into Team Foundation Server. This means that you can choose between using a checkout/edit/checkin model (TFVC "server workspaces"), a much more relaxed edit/merge/commit model (TFVC "local workspaces") or a DVCS (Git). I hope that wasn't too marketing speak-y. Anyway, sorry things feel clunky. I would definitely suggest moving from a server workspace to a local workspace if you haven't already and don't need some of the guarantees it makes about locking files for checkout and such. An edit/merge/commit system isn't nearly as chatty with the server and is much more pleasant to use on a daily basis.