I have a new Win7 VM with VS2013 freshly installed, so I'll install SSMS 2012 and see what happens, see if (or how much) footprint of VS2010 comes along with it -- Greg
On 3 November 2013 15:20, GregAtGregLowDotCom <[email protected]> wrote: > Same logic applies to SSMS2008 and SSMS2008R2 and their dependency on the > VS2008 shell. > > > > Regards, > > > > Greg > > > > Dr Greg Low > > > > 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 > fax > > SQL Down Under | Web: www.sqldownunder.com > > > > *From:* [email protected] [mailto: > [email protected]] *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 shell. That’s like trying to run a VS2010 add-in without > VS2010. > > > > Regards, > > > > Greg > > > > Dr Greg Low > > > > 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 > fax > > SQL Down Under | Web: www.sqldownunder.com > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *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 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 > registry to try and get clues about which products have their lives > entwined with VS2010, then see if it's safe to attempt to untangle them. > > > > Greg K >
