Comments
3 comments
-
I believe i found the resolution. Went into registry and backedup/deletes the addin node for 2008 R2 (not sure if config is possible but please note that if you run both 2008 and 2008 R2 you will lose tools in 2008)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\100\Tools\Shell\AddIns\RedGate.SQLSourceControl.MasterComAddIn
I did confirm I can still access SQL Source Control from 2005. -
Glad you sorted out this issue. I think your workaround will be be useful to other early access users!
Kind regards,
David Atkinson
Red Gate Software -
In EA2 (v0.2.1 - available on 22 Feb), we added a check that if you are using SSMS 2008 R2, we don't raise an error anymore, but just provide notification that SQL Source Control is currently unavailable for SSMS 2008 R2. This should mean that you shouldn't have to change your registry settings and can still work with SQL Source Control in SSMS 2005 for now.
Add comment
Please sign in to leave a comment.
Is there a way to do this?