VSIP "padlocks" in solution explorer don't always update

[ian_sg]

By way of setting expectations: we sort of intentionally broke this in 4.1.3, and fixing it won't happen soon.

In 4.1.2 and earlier, when you check out a file, we searched the whole solution explorer tree for any relevant nodes to update, which is necessary to find any link nodes like you've got. Understandably, however, this was slow on large solutions. And because we check out when you edit a file, this slowness was pretty painful every time you tried to edit a file that wasn't yet checked out.

To mitigate this, we now update only the one directly relevant node. It's lightning fast, but linked nodes don't get updated. In the common case, this is far better.

The way to solve both problems (update all relevant nodes and be fast) is to have some kind of cached index of files to solution explorer nodes. This is on the to-do list, but it's beyond the scope of what we'd do for a 4.1.x release.

Sorry for the inconvenience.

[tomt84]

No chance of getting a checkbox in the options to allow toggling between the 4.1.2 and 4.1.3 behaviour, with the default set in favour of 4.1.3?

This is a shame for us because we have a "relatively" small solution (circa 15 projects), but we make very heavy use of solution folders.

[lbauer]

This has been logged as bug 13716. We don't have a time schedule yet for fixing this,though.