Thanks for this, I'll try to review properly when I have some time available. A couple of comments/questions off the top of my head:

1. Are these the C# way of doing DocBlocks?

/// <summary>
/// Handle a connection to the simulator
/// </summary>
/// <param name="sender">SimConnect Object</param>
/// <param name="data">Simulator info</param>

2. Is your code using the C++ code in any way, or is this from scratch?
3. It would be nice to have everything under a single Solution as opposed to having two separate ones. If we're going to have two separate solutions, I propose we clean up the folder structure.
4. I see you based your code off of master as opposed to develop. Can you make sure you're using the same .editorconfig?
5. It'd be nice if the code style roughly matched what we use for C++. We can probably use this for C#.

1. Yep. That will create an XML file with the documentation that goes with the DLL
2. From scratch. I obviously copied a lot from the C++ side, but it's not linking to it or doing any code generation. I made a small change from the original PR to be more consistent with "Request"
3. Moved to main solution.
4. Retargeted to develop
5. This one's always touchy. That google style guide is a weird "Make C# look like C++" thing that I haven't run into before. Following the Microsoft Style Guide is much more common. Google referenced this, then changed a whole bunch of things. I updated the .editorconfig with the rules referenced in the Microsoft style guide, and updated my code to follow them. I'd rather follow these rules since it's much more in line with other C# project, but your house your rules, I'll change it over if you'd like.

Hey @frankracis, thanks for your patience - I've been quite busy. I've had some time to think about this and I have two issues with this PR at the moment (nothing to do with your code 😄):

1. The actual Jetbridge protocol will be evolving quite rapidly over the next few weeks. Since we are still in pre-release this will involve breaking changes, meaning that a lot of work would need to be done to keep this separate client up to date.
2. I'm not sure whether having these clients in the same repo is the right thing to do - especially considering that I won't really be using the C# client personally so I can't really maintain it. I think that having a separate repo maintained by others would make more sense.

I'm open to discussing this further. Let me know what you think 😃

That makes sense - you don't want ownership of code when you're not going to be responsible for maintaining it.

I'll create my own repo for the C# client, and you can just keep a link to it here.

That makes sense - you don't want ownership of code when you're not going to be responsible for maintaining it.

I'll create my own repo for the C# client, and you can just keep a link to it here.

I will be interested to use your client for opena3xx