News for hackers. Stuff that matters.

A comment on Microsoft Dependency Has Risks. Parent comment

Re:Microsoft Dependency Has Risks by cyberax on Thursday June 26, 2025 @03:24PM (#44390460)
And how do you _build_ it? "It works on my machine", yeah? "Just copy it", ya?
[ Parent | on HN ]
Re:Microsoft Dependency Has Risks by jongalloway2 on Thursday June 26, 2025 @04:24PM (#44390935)
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.

[ Parent | on HN ]
Re:Microsoft Dependency Has Risks by cyberax on Thursday June 26, 2025 @08:12PM (#44392704)
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.

[ Parent | on HN ]
Re:Microsoft Dependency Has Risks by jiggawatts on Friday June 27, 2025 @05:54AM (#44395410)
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.

[ Parent | on HN ]