Comments
Sort by recent activity
Understood, I see this in SQL Compare 6 and was just using the default folder.
This is a workaround, but it will still be a major issue with any project list containing an unavailable script folder. The timeout should only be a few seconds to determine the folder is unavailable. If the timeout cannot be limited, there should at least be a status showing you what it is happening and give the ability to cancel while it is verifying instead of hanging the application for several minutes without any indication of what is going on. / comments
Understood, I see this in SQL Compare 6 and was just using the default folder.
This is a workaround, but it will still be a major issue with any project list containing an unavailable script folder...
I don't understand what you mean by splitting the projects up. There is a single project list and it gets loaded the moment SQL Compare is started, so just launching SQL Compare causes the timeout issues as it immediately starts validating all the projects.
The issue isn't with the validation, the fact that the validation occurs on the project page and the fact that the validation can take several minutes to timeout causes it to be unusable for paths that may not be present at all times. If either of these conditions was changed, it would fix this bug.
My condition this week was that I needed to script a new project, but couldn't do so without waiting a few minutes for SQL Compare to load as it timed out on the project paths. I then simply wanted to delete the nonexistent projects and it took about 15 minutes of waiting for timeouts (timeout on load, timeout when the project line was selected, timeout when clicked "delete" which for some reason reloaded the project list and caused another timeout) to simply click the delete button. / comments
I don't understand what you mean by splitting the projects up. There is a single project list and it gets loaded the moment SQL Compare is started, so just launching SQL Compare causes the timeout...