[Question] Settings and DependentExtensionJson?

[GFlisch]

I am building an extension based on the same principal as the Sample: CompositExtension.
But in the OutOfProcComponent project I add a Settings capability like the sample: SettingsSample.

When doing this, I start to see an error when building the solution: Depedent extension.json property settings is not an array.

From my understanding, during the build 2 files are generated:

• extension.json
• settingsRegistration.json.

The extension is containing a settings section:
"settings": {
"registrationFilePath": ".vsextension\settingsRegistration.json",
"cacheTag": 639105850693486185
},

And the extension file is copied from the OutOfProcComponent to the CompositeExtension project thanks to the:

I imagine that the issue is that the settingsRegistration.json file is not merged in a CompositeExtension settingsRegistration.json file (that is not there)?
Is there a DependencySettingsRegistrationJson custom build task?

Can you guide me how to fix this issue?

Thanks in advance.

[sboulema]

Also ran into this :(

Figured it had to do with the Preview state of the options feature.

Worked around it by saving my options to a separate json file...

[GFlisch]

After using Claude, the project has been updated and now it works.
The equivalent CompositExtension csproj has been updated with this:



<_SettingsRegSource>$(MSBuildThisFileDirectory)..\Arc4u.Blueprint.OutOfProcComponent\bin$(Configuration)\net8.0-windows8.0.vsextension\settingsRegistration.json</_SettingsRegSource>
<_CompositeExtensionJson>$(OutputPath).vsextension\extension.json</_CompositeExtensionJson>

And a ps1 file:
param(
[string]$ExtensionJsonPath,
[string]$SettingsRegistrationSource
)

Inject the "settings" object into the composite extension.json after the

DependentExtensionJson merge, so VS can find the settings registration at runtime.

$json = Get-Content $ExtensionJsonPath -Raw | ConvertFrom-Json

if (-not $json.PSObject.Properties['settings'] -and (Test-Path $SettingsRegistrationSource)) {
$regJson = Get-Content $SettingsRegistrationSource -Raw
$cacheTag = long
$settings = [PSCustomObject]@{
registrationFilePath = ".vsextension\settingsRegistration.json"
cacheTag = $cacheTag
}
$json | Add-Member -NotePropertyName 'settings' -NotePropertyValue $settings
$json | ConvertTo-Json -Depth 20 | Set-Content $ExtensionJsonPath -Encoding UTF8
}

And in the OutOfProcComponent one, I have this:



<_ExtensionJsonPath>$(OutputPath).vsextension\extension.json</_ExtensionJsonPath>

With
param([string]$Path)

Remove the "settings" property from the dependent extension.json so the

DependentExtensionJson merge does not fail (it requires all properties to be arrays).

The settings entry will be injected directly into the composite extension.json instead.

$json = Get-Content $Path -Raw | ConvertFrom-Json
if ($json.PSObject.Properties['settings']) {
$json.PSObject.Properties.Remove('settings')
$json | ConvertTo-Json -Depth 20 | Set-Content $Path -Encoding UTF8
}

And I have the settings in the Options menu...

Be imaptient to have a better integration in the future.