add C# language support documentation

[bacongobbler]

closes #148

[bacongobbler]

Note that we're currently debugging an issue upstream for Linux support in Zulip. Once that's resolved, I think this should be safe to merge.

CC @jsturtevant

[kate-goldenring]

@bacongobbler thank you for putting this up! Is the c# tooling in a place where it can also create library components that target specific wit worlds? Could we add, whether in this PR or a follow up one, documentation on how to create a component that targets the example world? That is our prevailing example for the language guides. For example: https://github.com/bytecodealliance/component-docs/blob/main/component-model/src/language-support/python.md

[jsturtevant]

Is the c# tooling in a place where it can also create library components that target specific wit worlds?

It is we do this with https://github.com/bytecodealliance/componentize-dotnet/tree/main/samples/calculator/Adder

[bacongobbler]

Okay. I updated the documentation to show how to create a component that targets the example world as well as a second component that targets the hostapp world. Let me know if you'd like me to change and/or rearrange things.

As I was completing the document, I was looking for a way to execute these two components together and found this document on running components. However when I tried to run it, I saw that wasm-tools compose has been deprecated.

@jsturtevant I saw in your examples that you just created a dummy csproj that composes the two components together. Would you recommend suggesting that to new users, or is there a better approach you'd suggest? EDIT: answered my own question; see next comment

[bacongobbler]

I see that the composed example utilizes wasm-tools compose, which I assume isn't sustainable long term because it's been deprecated by the maintainers. Are there other ways within C# that we can compose two modules and execute them via wasmtime similar to the python example? is wasmtime-dotnet stable enough for this purpose?

[bacongobbler]

Doesn't seem like it at the moment 😭

bytecodealliance/wasmtime-dotnet#324

[kate-goldenring]

@bacongobbler does wac plug work? I have a pr #154 switching the docs to use that instead of wasm-tools compose but if you can only use wasm-tools compose for now, that is better than nothing

[jsturtevant]

yes you can use a dummy project or in the final project can compose them together.

Doesn't seem like it at the moment 😭

bytecodealliance/wasmtime-dotnet#324

this is only if you want to use .net as the host to execute components. As @kate-goldenring mentions Wac is the way forward to compose two components together

As far as including wac in the package so its easy; its been my list for awhile but probably won't get to it till its a forced 😆 bytecodealliance/componentize-dotnet#5

[bacongobbler]

Updated to use wac plug

[kate-goldenring]

Thank you for making this so comprehensive @bacongobbler. My comments are mainly nits with the main suggestions being around command component terminology and renaming that component executable.

We should also add reference to this document to language-support.md, introduction.md and SUMMARY.md but that can be done in a subsequent PR too

[kate-goldenring]

LGTM! Thank you @bacongobbler for putting this together. This will expedite users' c# experience.