Skip to content

Improve COM inproc initialization - #6607

Merged
JohnMcPMS merged 3 commits into
microsoft:masterfrom
JohnMcPMS:fix/defer-inproc-initialization
Oct 22, 2026
Merged

JohnMcPMS merged 3 commits into
microsoft:masterfrom
JohnMcPMS:fix/defer-inproc-initialization

Conversation

@JohnMcPMS

@JohnMcPMS JohnMcPMS commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

📖 Description

Move initialization out of DllMain for the inproc module; the initialization is doing too much to be done there.

Make file logging best effort; if file logging is blocked for some reason, we won't get any logs and nothing will work. Let callers attempt to operate, although if the temp location is blocked for some reason we will likely fail later.

🔍 Validation

Added tests for scenario where logging location is blocked.

Microsoft Reviewers: Open in CodeFlow

@JohnMcPMS
JohnMcPMS requested a review from a team as a code owner October 21, 2026 17:30

@ranm-msft ranm-msft left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Initialization now stays outside DllMain and remains once-only across both activation exports. The blocked-log-path unit and activation tests cover the nonfatal logging path, and the current builds and tests are green.

@JohnMcPMS
JohnMcPMS merged commit bc1e9ff into microsoft:master Oct 22, 2026
9 checks passed
@JohnMcPMS
JohnMcPMS deleted the fix/defer-inproc-initialization branch October 22, 2026 22:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants