Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Harden reg-free class activation #3365

Merged
merged 1 commit into from
Dec 9, 2024
Merged

Harden reg-free class activation #3365

merged 1 commit into from
Dec 9, 2024

Conversation

kennykerr
Copy link
Collaborator

Reg-free activation should only be attempted if the class is not registered.
It should not be attempted if the class is registered but fails to activate.

Fixes: #3339

@riverar
Copy link
Collaborator

riverar commented Dec 9, 2024

What about the E_NOINTERFACE scenario?

@riverar
Copy link
Collaborator

riverar commented Dec 9, 2024

After reflecting on it more ☕... I suppose if I ask you to grab the meat from the fridge and you check, only to find it empty, that should conclude the task. I wouldn't want you searching elsewhere or making assumptions about where else it might be. Looks good to me.

@kennykerr
Copy link
Collaborator Author

kennykerr commented Dec 9, 2024

Yes, this ensures that it does not accidentally "fall through" and attempt reg-free when activation should legitimately fail for one reason or another. This is a simplified version of what's being done here for cppwinrt.

@kennykerr kennykerr merged commit b2ce31d into master Dec 9, 2024
75 checks passed
@kennykerr kennykerr deleted the harden-reg-free branch December 9, 2024 16:31
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.

Reg-free activation should only kick in for REGDB_E_CLASSNOTREG
2 participants