Well, yes, that API call comes with linking to shell32.dll, which effectively hosts parts of Explorer (including shell extensions) in your process. The person you replied to probably suggested that Chrome would sandbox the common dialogs in its own new process to avoid potential issues. Just like they put, e.g. Flash into its own helper process without Flash being its own executable.