Winget configuration --package-id

[Stephanevg]

Hey all, I hope asking this question here is ok. Please redirect if this is the wrong place.

I was looking into winget configuration --package-id and when I exported the configuration from my visual studio code, using this command

winget configure export --package-id "Microsoft.VisualStudioCode" -o ".\Winget.Export.VsCode.json"

I got only this.

Winget.Export.VsCode.json

# Created using winget configure export 1.11.430
# yaml-language-server: $schema=https://aka.ms/configuration-dsc-schema/0.3
$schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json
metadata:
  winget:
    processor:
      identifier: "dscv3"
resources:
- name: winget_Microsoft.VisualStudioCode
  type: Microsoft.WinGet/Package
  metadata:
    description: "Install Microsoft.VisualStudioCode"
  properties:
    id: "Microsoft.VisualStudioCode"
    source: "winget"

The thing is, is that I was hoping to see things like my extensions, maybe some settings etc...

Was I missing a parameter maybe ? Is this maybe not how this works ?

I coudln't find much info on this in the docs... :/ Any guidance would be much appreciated.

[kilasuit]

I don't think this is how it works because it is more often than not seen that you are more than likely to sign into VSCode and pull down your profile from either Microsoft Account / GitHub and that repos will make use of .vscode\extensions.json files if that is the editor of choice to ensure the editing experience is similar for all involved.

I recall there was in other PowerShell based DSC Resources like Ravi's vscode DSC Resource Module from 2016 the ability to extract the extensions as well.

This would need a specialist DSC v3 VSCode resource which is already available in the winget-dsc repo in the samples folder & has samples for this exact usecase.

Hope that helps & this can be marked as the answer here!