It's not a game-changer for me. I like to have it, but I'm also still using tools like NimbleText and thinking about source generators for a lot of stuff. Source: about 1 year ago

Writing a program to generate some tedious C# is actually a fine endeavor. I've done it plenty of times! You should also have a look at NimbleText. Then you don't even have to write 80% of the script! Source: about 1 year ago

That gets really, really old really, really fast. Every control you write probably has 2-5 of these, and in extreme cases a control might have more than a dozen. I already use the templating tool NimbleText to help with this. It'd be a lot nicer if I could just write a prompt like:. Source: about 1 year ago

That said, if you don't feel like waiting around to see if I actually do the example (I don't always keep these promises), for stuff like this there's a tool called NimbleText I've been using to generate the class for me. There's a free online version that will do the trick and it doesn't take too long to figure out. The main "downside" compared to source generation is you have to copy/paste it yourself. Source: over 1 year ago

NimbleText lets me write a template for one instance of that code, then I can fill in data lines and let it generate the rest. It's kind of like a source generator, only at write-time, not compile-time. It's done more work to make dependency properties palatable than Microsoft ever has. Source: over 1 year ago

Just give it a try to https://analyzati.com. Source: over 1 year ago