this post was submitted on 28 Mar 2024
17 points (90.5% liked)
Programming
17496 readers
35 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've never needed to use a template processor to generate code. Usually a macro system built into the programming language is better for this. I think template processors are more commonly used for generating text documents.
What problem are you trying to solve?
The most common usecase is generating data models based on the database, mostly using t4 files so far. We have a non-standard way of defining some parts of it so the default MS tools don't quite cut it (like ef dbcontext scaffold). I've been looking into roslyn but it seems like it might be more trouble than its worth, but default t4 doesn't even have a proper editor and syntax highlighting so its a low bar atm.
If you're writing C#, you could take a look into Source Generators. They're supported directly by Roslyn I believe, and are pure C# instead of t4's syntax. They're often used with attributes to augment types, but I believe they can be used to generate sources on their own, and even read from a config file if you want to (or maybe even query the DB, if that's something you want to do at build time for some reason, though I've never tried this).
Is it prohibitively expensive to manually define your data types? How many do you have?
I do not generally recommend using ORMs, but this advice is likely dependent on the particular ecosystem you are dealing with.
It seems like you are pretty deep into Microsoft/.NET territory. I don't have any experience with .NET so I might not be the best person to help.