Schema Compare Options dialog closes when expanding a node on Object Types tab - by Đonny

Status : 


Sign in
to vote
ID 785638 Comments
Status Active Workarounds
Type Bug Repros 7
Opened 4/25/2013 10:52:35 PM
Access Restriction Public


When I go to Schema Compare Options dialog (of scmp file in database project), goto Object Types tab there and try to expand aither Application-scoped or Non-Application-scoped node the dialog closes giving me no chance to adjust the options.
Sign in to post a comment.
Posted by nwdavisMsConnect on 4/7/2017 at 3:53 PM
When I saw this occur, I had a saved schema comparison that was comparing a project with a database. When I reopened it, I encountered this behavior (but it might not necessarily have been the first time I reopened it). I had also recently restored the database to a snapshot, after opening the solution (but I believe I had the schema compare closed when I actually did the restore).

The work around for me was to close visual studio, us tfs power tools to scorch "tfpt scorch /recursive /exclude:*.suo,*.user" then reopen the solution. I then reopened my saved schema comparison. After doing that, the the options no longer closed when trying to expand/collapse the object type nodes.
Posted by Shiftkey on 8/5/2016 at 1:40 AM
Happened to me too with VS2015.3 with SSDT 14.0.60629.0. Not only on expanding a node but also (un)checking a checkbox option.
Thanks to Manual_R for pointing out that keyboard navigation does work. For me, after using keyboard navigation once to change a setting, and then saving the scmp file, the dialog is now working correctly again, also with the mouse.
Posted by Manuel_R on 4/21/2016 at 1:05 AM
Regardless of there being a workaround present (reset settings), this bug is sill present in SQL Server Data Tools build 60311.1 (e.g. SQL Server Data Tools 14.0.60311.1 in Visual Studio Enterprise 2015 Update 2).
Navigating with the keyboard works fine. Expanding a node with the mouse is affected by this bug.
Posted by rohancragg on 11/13/2014 at 6:46 AM
This just happened to me in VS2013.4 too.
I cleaned / re-built the .dbproj project, closed and re-opened VS and it fixed for me.
Posted by jvrobert on 10/28/2014 at 12:47 AM
Same issue, versions, and solution as Andrzej - resetting VS settings seems to fix it.
Posted by Andrzej Stolarczyk (Andrew) on 10/6/2014 at 6:22 AM
After reseting VS settings it just works fine.
Posted by Andrzej Stolarczyk (Andrew) on 10/3/2014 at 6:25 AM
I have the same issue on VS2013 U3 and SSDT 12.0.40706.0

I noticed that it only happens when I use mouse. I tried to select any option with keyboard and the window didn't close :)
Posted by Justin Adkins on 9/10/2014 at 8:32 AM
It's happened to me in VS2012 Update 4 and VS2013 Update 3.
SQL Server Data Tools Version 12.0.40706.0
Microsoft SQL Server Analysis Services Designer Version 12.0.2000.8
Microsoft SQL Server Integration Services Designer Version 12.0.2344.23
Microsoft SQL Server Reporting Services Designers Version 12.0.2344.23
Posted by Justin Adkins on 9/10/2014 at 8:29 AM
I've also experienced this same bug. However, it also happens whenever I attempt to 'check' any of the items.
Posted by Microsoft on 7/3/2013 at 9:04 AM
Could you try Tools.Import and Export.Reset to reset all your settings? We were unable to repro. Also, there's a June 2013 release of SSDT available that may fix the issue.
Posted by Microsoft on 5/30/2013 at 3:15 PM
Sorry for the delay, Donny. Are you still seeing this issue? If so, could you provide some more details, as we are unable to reproduce the problem? Here are a few questions I have that may help us troubleshoot:

1) What version and sku of VS are you using?
2) Have you installed SSDT separately from the web and if so, which version?
3) Do you know how the .scmp file was created? For example, was it created by a different version of SSDT than the one you are using?
4) If you open that same .scmp file on a different machine, do you see the same behavior?


Posted by Microsoft on 4/28/2013 at 7:38 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 4/25/2013 at 11:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(