Maira Wenzel

Results 230 comments of Maira Wenzel

After running mdoc 5.7.4.9, this list is reduced. Currently, the following attached properties are still missing: * System.Windows.Shell.WindowChrome.ResizeGripDirection * System.Windows.Localization.Attributes * System.Diagnostics.PresentationTraceSources.TraceLevel

Another thing I've noticed is that some of the ones that were added are only identified as .NET Core 3.0. Different issue? Example: https://docs.microsoft.com/en-us/dotnet/api/system.windows.navigation.baseurihelper.baseuri?view=netcore-3.0

Adding some other missing APIs to the list: - System.Windows.Shell.WindowChrome.IsHitTestVisibleInChrome - System.Windows.Shell.WindowChrome.ResizeGripDirection - System.Windows.Localization.Attributes - System.Windows.Localization.Comments - System.Diagnostics.PresentationTraceSources.TraceLevel

The current list of missing attached properties: - System.Windows.Shell.WindowChrome.IsHitTestVisibleInChrome - System.Windows.Shell.WindowChrome.ResizeGripDirection - System.Windows.Localization.Attributes - System.Windows.Localization.Comments - System.Diagnostics.PresentationTraceSources.TraceLevel I'd check with @SamBent the expectation/definition of attached properties and whether they can...

Found one more while validating the latest IntelliSense: https://msdn.microsoft.com/en-us/library/system.windows.media.animation.storyboard.targetproperty?toc=xxx This was erroneously redirected to https://docs.microsoft.com/en-us/dotnet/api/system.windows.media.animation.storyboard.targetproperty I also noticed that the link from https://docs.microsoft.com/en-us/dotnet/api/system.windows.media.animation.storyboard.targetpropertyproperty?view=netframework-4.8 summary goes to the field, even though...

You can just rename the labels and check if you have any docs that point to the old label.

In what path are you trying to create the app? Did the error message contain any other details?