| Author |
 Topic  |
|
|
WolfgangVogl
Junior Member
Germany
11 Posts |
 Posted - May 04 2018 : 07:31:11 AM
|
Is it possible to have an configuration which is stored in an solution related directory as a file?
As a team we're all working on the same solution (organized by a git repository) and we would like to share some configrations (for example, the "Enable Source Links" Feature).
Is it possible to push a visual assist configuration file into our git repository that enables this feature with a specific line? (in addition to the individual configuration) |
Yes, we code! |
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - May 04 2018 : 07:59:36 AM
|
At this time, no. But we received a lot of feedback about Source Links at GDC that shared per-solution configuration for Source Links definitions that is distributed alongside the source is REALLY wanted, so we plan on making that happen.
Do have any other configuration that you want to share in such a manner? |
Edited by - sean on May 04 2018 08:00:36 AM |
 |
|
|
feline
Whole Tomato Software
United Kingdom
18749 Posts |
Posted - May 04 2018 : 08:09:17 AM
|
For now, if you don't mind using a script to both set the VA options you want, and then load the matching solution, you could use a script file to first set the registry settings / import a .reg file, for the settings you want, and then load the matching solution by launching "devenv.exe" and passing the SLN as a command line parameter.
A lot less elegant, but it would give you files that can be checked into source control. |
zen is the art of being at one with the two'ness |
|
|
|
WolfgangVogl
Junior Member
Germany
11 Posts |
Posted - May 04 2018 : 08:11:16 AM
|
@sean: Sounds promising!
Indirectly, yes - nearly every possible VA option (in special the whole code-inspection properties) in the manner of a default value / suggestion by the team (everyone should be able to overwrite the option by himself).
(a "overwrite" mechanism: -> VA default -> "Team configuration default" -> individual configuration)
But the most concrete/direct need is indeed the source links section.
@feline: yeah but that's not working in our team because if you decide to change a value someone needs to export the reg file and everyone needs to checkout and remember to double click... (yes it's strange that people can write complex software but they're not able to remember to do a double-click.. :-( ) |
Yes, we code! |
Edited by - WolfgangVogl on May 04 2018 08:17:21 AM |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - May 04 2018 : 1:22:34 PM
|
Feature request for per-solution Code Inspection configuration sharing is case=116257.
Feature request for per-solution Source Links configuration sharing is case=115282. |
|
|
|
WolfgangVogl
Junior Member
Germany
11 Posts |
Posted - May 07 2018 : 01:14:47 AM
|
| Is there a issue/feature tracking system where i can track the cases? |
Yes, we code! |
|
|
|
feline
Whole Tomato Software
United Kingdom
18749 Posts |
Posted - May 07 2018 : 11:10:05 AM
|
Unfortunately our case list is not publicly visible. We do update the forum threads when a case that is referenced in the thread is fixed, and the case numbers are also listed in our history of changes page.
You can ask for an update on a case, to find out how things are going. We have quite a lot of feature requests, so some take longer to address than others, partly depending on how popular a request seems to be. |
zen is the art of being at one with the two'ness |
|
|
|
FriendlyRabbit
Junior Member
Germany
16 Posts |
Posted - Sep 25 2023 : 02:53:57 AM
|
I would like to have what WolfgangVogl suggested. In our team we need a way to synchronize which code inspections are enabled.
Ideally, I have a list of minimal code inspections (+ configuration), which all developers use. Additionally, I want to allow them to enable additional code inspections they like. |
|
|
|
feline
Whole Tomato Software
United Kingdom
18749 Posts |
Posted - Sep 25 2023 : 10:20:56 AM
|
This is still something we are looking to add. For now, if you want to start everyone off with standard set of settings, you can configure code inspection how you want, then export the VA settings:
VA Options -> Performance -> Export Settings
then you can delete the general settings, leaving the code inspection blocks. Not the most straight forward solution I know, but it might help in getting everyone to start at the same point. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
Configuration per Solution / shared configuration
