Yeah it can be a little confusing until you realise the version is not tied to
the product name or release year.
Lucky Microsoft don't skip version numbers. Otherwise they could catch up to
the matching year and cause more confusion.
...
Oh wait.
________________________________
From: ozdotnet-boun...@ozdotnet.com <ozdotnet-boun...@ozdotnet.com> on behalf
of David Gardiner <da...@gardiner.net.au>
Sent: Monday, 6 February 2017 12:56:50 PM
To: ozDotNet
Subject: Re: installing multiple things on my development machine. Are Virtual
machines still the way to go?
That would be the marketing team ("Visual Studio 2015") with the product team
(Visual Studio v14), or more recently Visual Studio 2017 (which is version 15)
The major version number increments each major release, the product name
changes too but it isn't tied to the version number. Looking at
https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#History, the only time
they've ever coincided was version 6 and 10 :-)
David
On 6 February 2017 at 15:01, mike smith
<meski...@gmail.com<mailto:meski...@gmail.com>> wrote:
On Mon, Feb 6, 2017 at 2:45 PM, Greg Keogh
<gfke...@gmail.com<mailto:gfke...@gmail.com>> wrote:
Do watch out for having too many versions of SQL Server installed - it can end
up making your PATH environment variable too big and then "bad things" start
happening.
I just had a look at my default login path for the first time in a year or so
and I'm shocked by finding the following items crammed into it.
C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\
C:\Program Files\Microsoft SQL Server\130\Tools\Binn\
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\
C:\Program Files (x86)\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\
C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\ManagementStudio\
Three versions no less! Even worse, under the x86 folder I find subfolders 80,
90, 100, 110, 120 and 130. Then nearby I noticed I also have Visual Studio
folders numbered 8, 10.0, 11.0, 12.0 and 14.0. What a mess.
While I'm in a ranty mood, why is VS out of step, numerically, between its
splash year ( Visual Studio 2015 ) and its folder name C:\Program Files
(x86)\Microsoft Visual Studio 14.0 ??
And the name of the next version ?
The PATH is such on ancient concept I'm amazed it still exists in Windows. If
you go Win+R and enter excel.exe for example, it will run even though it's not
in the path. There are special registry entries for this magic lookup (I forget
where I saw them) but I've never seen documentation on how to exploit it for
your own use.
GK
--
Meski
http://courteous.ly/aAOZcv
"Going to Starbucks for coffee is like going to prison for sex. Sure, you'll
get it, but it's going to be rough" - Adam Hills
