.NET tooling alignment

[derberg]

I just onboarded https://github.com/asyncapi/net-sdk to AsyncAPI

There is also https://github.com/asyncapi/saunter/

This discussion shows there is a need for a dedicated discussion on functional alignment between these tools.

So please continue, in a async fassion here or if you can the org can help you facilitate a working group - is the discussion and execution needs some weeks/months,

Cc .NET folks that are involved in tooling development at AsyncAPI:
@cdavernas @JBBianchi @thompson-tomo @VisualBean @iancooper @m-wild @yurvon-screamo @connil @mr-nuno @dpwdec

[thompson-tomo]

To Start the discussion let me share a couple of questions which we should look to answer: * What is the primary library for hosting asyncapi documents? * What library handles document serialization? * What tool is responsible for generating api documents? * What tool is responsible for client generation? * What library adds ability for classes to be populated with attributes to provide info for the generated document? Is there an opportunity to align with the Kiota team to broaden that tools scope to also generate clients based on asyncapi documents as per point 4 above? With that, the asyncapi foundation would publish packages ie AsyncAPI.Kiota.Transport.RabbitMQ, AsyncAPI.Kiota.Parser.AsynAPI which implement interfaces provided by Kiota. *