Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio 2017 Release Candidate

visualstudio.com

Post reply on HN
Print view View original

101–110 of 121 posts

Re: Visual Studio 2017 Release Candidate

#101

Post by mynameisvlad »

vram22 wrote: post #94
b_lindahl wrote: post #38

Visual Studio "15" = Visual Studio 2017 = VC 15.0 Crystal clear. Why didn't Microsoft bump up VC version to 17 to sort of make VC version follow VS version. Would clear out some confusion going forward.

Many software packages have poor or confusing version numbering. Java, IIRC, jumped from Java 1.2 to 2 or 1.4 to 4 or something like that. Windows 3.1 to 95 to 98 to Me to NT (stood for New Technology, ha ha [1]) to 2000 to XP to Vista to 7 to 8 to 10 ... (might have got some of the order wrong there). [1] New, as in the classic marketing/advertising phrase "new and improved", maybe ... :)

NT was called "New Technology" literally because it was a new technology. It was based on the NT kernel (which is used now) as opposed to the 9x/MS-DOS kernels used in 1.0-Me.

Also, NT came before 95. Specifically, as Windows NT 3.1.

Re: Visual Studio 2017 Release Candidate

#102

Post by roel_v »

b_lindahl wrote: post #38

Visual Studio "15" = Visual Studio 2017 = VC 15.0 Crystal clear. Why didn't Microsoft bump up VC version to 17 to sort of make VC version follow VS version. Would clear out some confusion going forward.

Even the MS installers get this mixed up sometimes. Sp5 to vs 2015 mixed up some paths between vc12 and vc14.

Re: Visual Studio 2017 Release Candidate

#103

Post by gjm11 »

vram22 wrote: post #95
fetbaffe wrote: post #72

Earlier quoted context omitted.

No, 2017 written as separate numbers are 2 0 1 7 and adding them up gives 10. Half of 10 is 5 (obviously) and that sum is 15. Get it?

Call in Ramanujan. He'll surely come up with a good explanation. https://en.wikipedia.org/wiki/Srinivasa_Ramanujan#Hardy.E2.8...

"No! It is a very interesting number. It is the smallest positive integer that Microsoft have not yet used as a version number."

Re: Visual Studio 2017 Release Candidate

#105

Post by daemin »

b_lindahl wrote: post #38

Visual Studio "15" = Visual Studio 2017 = VC 15.0 Crystal clear. Why didn't Microsoft bump up VC version to 17 to sort of make VC version follow VS version. Would clear out some confusion going forward.

It's just a product with a name that has a year in it, but the executables inside each have their own different version.

For example for Visual Studio 2015, the visual studio executable is at version 14, and the C++ compiler is at version 19.

So would you also suggest changing the C++ compiler version back to 17 now?

Re: Visual Studio 2017 Release Candidate

#106

Post by bung »

gregmac wrote: post #65
b_lindahl wrote: post #38

Visual Studio "15" = Visual Studio 2017 = VC 15.0 Crystal clear. Why didn't Microsoft bump up VC version to 17 to sort of make VC version follow VS version. Would clear out some confusion going forward.

I am beginning to think that Microsoft's bad verison naming is entirely on-purpose. Windows has had terrible naming since NT -- back and forth between names/numbers/years (or nonsense like "Anniversary Update" or "R2"), have a completely different scheme for Server vs Desktop, and if you look at the corresponding kernel versions of these releases[0], the major/minor bump in versions seems completely arbitrary. .NET i…

On purpose... but any guess as to why?

Re: Visual Studio 2017 Release Candidate

#107

Post by oerpli »

gjm11 wrote: post #103
vram22 wrote: post #95

Earlier quoted context omitted.

Call in Ramanujan. He'll surely come up with a good explanation. https://en.wikipedia.org/wiki/Srinivasa_Ramanujan#Hardy.E2.8...

"No! It is a very interesting number. It is the smallest positive integer that Microsoft have not yet used as a version number."

Actually that would be 13.0!

Re: Visual Studio 2017 Release Candidate

#108

Post by LyalinDotCom »

PerfectElement wrote: post #40
omerraviv wrote: post #17

Some first impressions here: https://blog.oz-code.com/first-impressions-of-visual-studio-...

Thanks! I was hoping I would be able to get rid of ReSharper, but the lack of CamelHumps in navigation and in code completion will force me to keep using.

Visual Studio already supports Camel Hump search in IntelliSense and for symbols within GoTo. It’s currently missing for file names in Go To, but we’re working on that and it should be coming soon.

P.s. I work on the extended VS team.

Re: Visual Studio 2017 Release Candidate

#109

Post by cptskippy »

erikbye wrote: post #96
billforsternz wrote: post #61

Earlier quoted context omitted.

Indeed, .NET must be the worst, most misleading, least googleable product name ever. I suppose we should be grateful that MS called an earliest technology COM not .COM.

The first result I get googling for ".net" is the Wikipedia article ".NET Framework". The first result I get for "COM" (or "com") is Microsoft's page on "COM: Component Object Model Technologies". Honestly, I have never had a problem googling .NET and COM-related stuff.

It was mostly a problem when you were having a conversation with someone that went something like...

"So I was installing .NET and it failed because I didn't have the right drivers for my SCSI card."

"What? I've never needed disk drivers to install .NET, which version was it? 1.1?"

"No, it was 2003"

or...

"Can you install .NET on my PC?"

"Sure, done"

"Where's Word and Excel?"

"What?"

Re: Visual Studio 2017 Release Candidate

#110

Post by uabstraction »

Maarten88 wrote: post #81
billforsternz wrote: post #61

Earlier quoted context omitted.

Indeed, .NET must be the worst, most misleading, least googleable product name ever. I suppose we should be grateful that MS called an earliest technology COM not .COM.

I must say Google handles it well. I'm searching with these terms quite often and Google knows .NET == dotnet ~ C# and finds results without much problems.

Google is terrifyingly good at finding relevant developer documentation. I'm convinced it will be writing software for us in a couple years.
Post reply on HN