Update more controls documentation for c# markup

[cesm1980]

What would you like clarification on

I ask this since i had a lot of trouble figuring out how to use ShadowContainer using c# markup, which i eventually suceeded ONLY after resorting to chatgpt, since unfortunately there is no online xaml to c# markup and i am still a beginner on c# markup and even c# itself. I am sure more controls dont have c# markup parts as well, and unfortunately the uno gallery and uno playground are xaml only, i hope that later they will have c# markup examples too, altough of course meanwhile i am learning myself.

Concern

Support

Affected platforms

Windows (WinAppSDK)

Any feedback?

More examples of xaml to c# markup in the xaml snippets in controls documentation, specially those more complex with containers for example.

[MartinZikmund]

C# markup uses Source Generators, which generally just adds the appropriate static extension methods for each of the properties supported by each control. That being said, we definitely need to improve documentation in this area, so if you have specific controls/scenarios you are struggling with, please let us know and we can improve the documentation accordingly

[cesm1980]

Oh i see, thanks for the response, in the meanwhile i am studying c# mark more in-depth and i think this is the right choice since my problem was having lack of bases since after all i am still a newbie on c# markup, and even on XAML itself and c# (my main experience before this was winforms and vb.net, fortunately learning c# isnt being as difficult as i feared because of my experience in vb.net) but now i am understanding c# markup better and now being able to convert xaml to c# markup by myself a lot better, so yeah in case i find more specific suggestions i will give it indeed.

[cesm1980]

Well, for now ShadowContainer would be a huge help, so a c# markup version of the snippets on the shadowcontainer alongside the xaml ones would help a lot, altough i find strange that i wasnt' able to declare shadows as methods, and instead had to manually declare them using normal non-fluent api code to declare them, but at least i learned a lot of c# markup making this work :D but i wonder which other controls will be this hard to port to c# markup, i could add here on this comment as i find out, since i noticed the tag for triage/needs-information to work on it, so perhaps that would help then.