Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> with C code blended in randomly

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?



CSnakes integrates Python into .NET apps - https://tonybaloney.github.io/CSnakes/

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...


And how do you _build_ it? "It works on my machine", yeah? "Just copy it", ya?


dotnet build

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.


Nope. Try again.

> 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.


My point was that "copy" is sufficient and works much more robustly than with NPM/Node, for example.

At $dayjob I use DevOps agents or App Service with pipelines. I'm not a savage.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: