Hi Greg,
SSMS 2012 runs inside the VS2010 shell. It's probably not surprising that
removing VS2010 causes SSMS 2012 problems. I suppose it would be nice if
VS2010 had an understanding of all things that used its shell but it
doesn't. So running repair on SSMS 2012 would have just put back the
So running repair on SSMS 2012 would have just put back the components of
the VS2010 shell.
Oh drats! That's the reverse of what I'm trying to do. I've got to figure
out how to utterly remove VS2010 (if it's possible).
When I finish today's hobby coding I'll run a global search through the
: http://www.sqldownunder.com/ www.sqldownunder.com
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Greg Keogh
Sent: Sunday, 3 November 2013 1:28 PM
To: ozDotNet
Subject: Re: SQL Server Management Studio dependencies
So running repair on SSMS 2012
: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of GregAtGregLowDotCom
Sent: Sunday, 3 November 2013 3:19 PM
To: ozDotNet
Subject: RE: SQL Server Management Studio dependencies
You can't have SSMS2012 without some aspects of VS2010 as SSMS2012 lives
within the VS2010
Of *GregAtGregLowDotCom
*Sent:* Sunday, 3 November 2013 3:19 PM
*To:* ozDotNet
*Subject:* RE: SQL Server Management Studio dependencies
You can’t have SSMS2012 without some aspects of VS2010 as SSMS2012 lives
within the VS2010 shell. That’s like trying to run a VS2010 add-in without
VS2010
