Team-Shared settings not recognized in cmake projects Follow
it seems, as cmake projects have an empty solution name, the team shared layer is not loaded, even if its within the root project folder. Am I missing something? It has been working for quite a long time, when I simply named it to "sln.DotSettings" but nowadays it won't automatically get loaded.
Please sign in to leave a comment.
The empty name issue was fixed at some point, the settings file should now be named literally "Folder.DotSettings".
Thank you for your reply. This does indeed make something clear for me, as I had a ``Folder.DotSettings`` file in my folder, which seems then to load my ``sln.DotSettings`` file. But nevertheless, this seems broken for all my cmake projects. I always have to manually open that file after my projekt loads up in visual studio 2022.
This is how it looks now. I removed the previous Folder.DotSettings file and replaced it with the actual settings file. Either way, it doesn't work anymore:
As I said, all of my projects are unable to automatically load that file. Perhaps it has something to do with my recent switch to windows 11. Actually can't tell, when it broke for me.
Sorry, I don't quite understand your setup. Which file does not get loaded? Could you please send us your .DotSettings files?
You told me, that I need to name my team-shared settings file "Folder.DotSettings" and that it will then get loaded automatically. As you can see, there is indeed a "Folder.DotSettings" in the project root folder, but it doesn't show up on the right in the team-shared layer.
I have to manually select it via "open" and then it works as expected, but on the next project start-up, I have to do it again.
Even if I add a fresh and clean new settings file via those Buttons, it doesn't load it automatically.
You're right, something got broken and Folder.DotSettings does not get used automatically. I've filed https://youtrack.jetbrains.com/issue/RSRP-489369, we'll investigate.
As a fix seems to be ready for quite a while now, when are you going to release it?
The fix will be available in 2022.3 EAP builds, which should start coming out in September. In the meantime you can try using this build with the fix backported to 2022.2: https://download.jetbrains.com/resharper/privatebuilds/JetBrains.dotUltimate.2022.2.EAP9D.Checked.(222.0.20220816.161032-eap09d).exe