Any sample using NOESIS+WASM+NETCORE+C#
?

I am trying to use C# to render XAML over the browser. Is this possible?

Right now we are only providing this for Unity. Although nothing stops you from doing the same in C# SDK, but you will have to manually convert C# to Wasm.

Has there been any progress on supporting a WASM target for C#? That would be our primary reason to use Noesis GUI. We have done some experimenting with the Unity build for WASM and it is not practical for our application.

In your above comment you said it would be possible to manually convert C# to Wasm. Can you provide a working example of how this would be done?

No progress on C# for WASM for now. If this is critical for your project, I think we could include some kind of prioritization as part of the license.

Could you please elaborate on why Unity is not practical?

We want to create a purely 2D application that is portable to WebAssembly, Windows, Android and iOS. My experiments with Unity suggest that:
* It would require an additional unnecessary Unity license cost per developer
* The debugging environment for Unity is more awkward than working entirely within Visual Studio
* The Unity engine would unnecessarily bloat the shipping product
* Rendering in the Unity screen space does not anti-alias. Non-bitmapped controls don't look good.

If I'm wrong about any of these, I'm happy to be corrected.

Everything is correct but the last point.

Rendering in the Unity screen space does not anti-alias. Non-bitmapped controls don't look good.

Just enabing PPAA in Noesis View should fix this. All our examples should render without AA artifacts. If you don't get that, something is wrong.

Thanks for clarifying. That makes Unity a fallback option if we cannot get WebAssembly to work any other way.

Back to my earlier question - can you provide some information about how we would compile to WebAssembly from a .NET Framework project? We do not mind writing post-processing scripts and makefiles if that is what it takes, we just don't know what the toolchain is, nor how to invoke it.

Back to my earlier question - can you provide some information about how we would compile to WebAssembly from a .NET Framework project? We do not mind writing post-processing scripts and makefiles if that is what it takes, we just don't know what the toolchain is, nor how to invoke it.

I didn't have time to figure out the right solution. Mono to wasm seems to be interesting although experimental.

Thanks. I'll take a look. If we decide to go ahead on a Noesis Engine project we'll probably want to take you up on the offer to prioritize WebAssembly when we buy our license.