-
Notifications
You must be signed in to change notification settings - Fork 980
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
Implement IsAncestorSiteInDesignMode. #5375
Implement IsAncestorSiteInDesignMode. #5375
Conversation
I'm very much OK with going forward with the original proposed API as approved. |
Yes. I had a discussion about this today with @JeremyKuhne, and he said the same thing. |
Let's not block on licensing for this effort. |
No, I mean with a potential additional API. This should fly as it is now. |
@KlausLoeffelmann could you please clarify the reason why we didn't add this API to |
A Component is not part of the control's collection. It doesn't work that way. You could not traverse up to check a parent for being sited, since there isn't one. |
Fixes #4146.
Resolves #3300
[Update]: This is now implemented as originally planned.
Wrote a small Test app for this, which should also serve as a guidance for best practice.
It is currently here: https://github.com/KlausLoeffelmann/IsAncestorSiteInDesignMode/blob/main/README.md
Shows where and how to use correctly
DesignMode
andIsAncestorSiteInDesignMode
for (derived) Forms, UserControls hosted in Forms and Controls:Microsoft Reviewers: Open in CodeFlow