Andy (Steve) De George

Thank you for opening this issue. I'll add it to the backlog. If you would like to contribute, you can submit a fix by editing the original article. Click on...

Thank you for reporting this. This is a common issue throughout the WPF documentation. Various parts of the XAML are reused and split out. We've recently adopted a model where...

Thanks for the desire to contribute 👍 This is a actually a bit more complicated. First, a lot of the links don't work via github because of the syntax used....

I think we should turn this into a project issue which is to identify and fix all of the individual articles that have this problem. I'm going to edit it...

@netdragonboberb I'm not sure what article you're referencing. It doesn't seem though that it's related to WPF/WinForms which is what this repo is for?

I'll put a note in this article that it's different starting with .NET 5/Core. When this article gets migrated to .NET 5, I'll fix the wording completely. Thanks!

Thank you for this feedback! We'll look at getting this issue prioritized.

Yes it would be more useful. I'll add this to the backlog.

After doing some research I think we can update these how-to articles with a note about **User** settings. The overview for this doc area should probably mention something too. I...

@SonOfKorriban sorry for the delay in response. When issues like this aren't tied to documentation, you'll generally get a quicker response searching and asking on [StackOverflow](https://stackoverflow.com/). Positioning and stretching is...