C#

What's the Problem?

In Properties.xaml, the NavigationView is always the same size regardless of the number of MenuItems, resulting in blank spaces that cannot be dragged.

The area surrounded by the green line is the draggable area and the area surrounded by the red line is the NavigationView.
![Properties](https://user-images.gith

Please describe your bug

When the server is stopped it sends a notification to all connected WebSocket clients, the message looks like this:

{"MessageType":"ServerShuttingDown","MessageId":"d9fbbca3037344b689490d35ec2d4ed7","Data":""}

(id is unique)

Unfortunately it then just stops the server, ending the connection abruptly. It would be nice if the clients get properl

When writing the endpoint address of the packet received from the socket, we do not verify the output buffer is allocated, and has enough space to hold the endpoint address. We should verify sockAddrOutSize is non-zero at a minimum. Additionally, IPEndpoint can represent either an IPv4 address or an IPv6 address. If the socket receives a packet from an IPv6 address, but the client has only all

What's the Problem?

It is not any type of problem.

Solution/Idea

This project is currently missing the Code of Conduct. If you have any plan on adding that then I would be more than glad to do that for you by adding a PR for that. Please let me know what do you think about that.

Alternatives

According to Google:

A code of conduct defines standards for how to eng

We can build much smaller Mono runtime for .NET Core purposes by simply removing code we don't need in this configuration. We did a few easy initial steps but we can go much further.

This list is not comprehensive but parts like

• Culture Data
• Any PAL related code
• Unused icalls

MonoGame has a very long history of tutorials, some are as old as a decade and some even are still based on XNA (which is compatible with MonoGame for the most part, but different in regard to how to start a project).

Also, MonoGame is a stable API with a policy of "no breaking changes" when possible, which means that even very old tutorials

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$ref": "#/definitions/foo",
  "definitions": {
    "foo": {
      "type": "object",
      "properties": {
        "bar": {
          "$ref": "bar.json#"
        },
      },
      "required": [
        "bar"
      ],
    },
    "title": "foo"
  }
}

Running quicktype CLI with this Schema produces

Error

Various characters (e.g. |) if used in a Params will end up invalidating the generated markdown, causing it to render incorrectly. It'd be helpful if benchmarkdotnet could escape the markdown output, e.g. output \| instead of |.