SonarSource
v7 connected mode bindings being keyed on solution names is brittle
The new connected mode seems to be using simply the solution name as the key for associating a connected mode binding to a VS solution.
It's not at all uncommon for multiple solutions to have the same name while residing under separate folder structures. This can cause collisions and conflicts between different projects with different configuration needs.
Also; if solution names are changed during the course of a project's life time, the connected mode bindings become disassociated as well. This violates principle of least surprise.
@rjgotten thanks for the feedback. Can you give an example of where you would commonly use the same name for multiple solutions in production please?
cc @marco-comi-sonarsource
@rjgotten thanks for the feedback. Can you give an example of where you would commonly use the same name for multiple solutions in production please?
cc @marco-comi-sonarsource
Same project structure being maintained for multiple clients, residing in different folder names named after the client.
So rather than [..]/<client>.<solution>.sln you get [..]/client/<solution>.sln.