And now add a small Python neural network to a .NET app. Just to do some mild AI stuff. Go on, I'll wait.
Oh, and I forgot: don't forget about data migrations. It's a freaking disaster in .NET deployments. Apparently, the best practice is to apply them manually?
https://www.youtube.com/watch?v=DqoxHNH9Iwo shows adding an LLM
There are several ways to manage migrations depending on the team structure and dev practices: SQL scripts, command line, bundles (single-file executables), and in-app. The team recommends SQL scripts since they can be reviewed, tuned, and managed by a DBA but take your pick. https://learn.microsoft.com/ef/core/managing-schemas/migrati...
https://tonybaloney.github.io/CSnakes/getting-started/#build...
What's with the "just copy it" thing? Nobody does that, we use NuGet packages, GitHub Actions, SDK supported containers, reproducible cross-platform builds from command line, etc.
edit: I'm sure some people use file/copy, but you sure don't have to. That stopped being a common thing 10+ years ago with cross-platform .NET.
> Nobody does that
Read the parent post.
> we use NuGet packages, GitHub Actions, SDK supported containers, reproducible cross-platform builds from command line, etc.
So basically, "NPM but different". Got it.
At $dayjob I use DevOps agents or App Service with pipelines. I'm not a savage.