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 components of the VS2010 shell. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: <http://www.sqldownunder.com/> www.sqldownunder.com From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Saturday, 2 November 2013 7:46 PM To: ozDotNet Subject: SQL Server Management Studio dependencies Here's a bit of a warning ... Last week I uninstalled VS2010 as it was running alongside VS2012 and it was of no use any more. Tonight I launch SSMS 2012 and it says required components are missing and tells me to reinstall. Web searches produce lots of hits, and suggestions about deleting registry keys are worthless. I ran the SSMS 2012 installer exe again and picked "Repair". This miraculously made it work again. I also noticed that the registry keys under SSMS have dozens of references to VS2010 folders. I changed some of the more obvious ones to point to equivalent VS2012 folders, which fixed some other warning popups that I was getting. So basically there is an unholy tangle of dependencies between SSMS and VS versions more subtle than I suspected, so be careful. I look forward to building a brand new machine next Xmas to clear all of the detritus out. I'm always irritated by the way many "big" products don't uninstall so easily or so cleanly, leaving fragments all over the place. Greg K
