← Back to context

Comment by malkia

11 days ago

Or... you can

"winget install Microsoft.VisualStudio.BuildTools"

"winget install Microsoft.WindowsSDK.10.0.26100"

7 comments

malkia

Reply
macshome  11 days ago

I thought for a moment I was missing something here. I always just use winget for this sort of thing as well. It may kickoff a bunch of things, but it’s pretty low effort and reliable.

scotty79  11 days ago

But those are installed system wide. What if you have two different project with different requirements at the same time?

Every language should have a tool like Python uv.

  • Const-me  11 days ago

    > What if you have two different project with different requirements at the same time?

    Install multiple versions of Windows SDK. They co-exist just fine; new versions don’t replace old ones. When I was an independent contractor, I had 4 versions of visual studio and 10 versions of windows SDK all installed at once, different projects used different ones.

    • malkia  11 days ago

      You can provide custom options to winget, and in there where to install it too (and additional components you need).

  • smileybarry  10 days ago

    Windows SDKs, WDKs (driver dev), Visual Studio releases, and .NET SDKs all coexist peacefully on a machine. If a project build breaks due to newer SDKs, it's because it was configured with "use newest version". (Which is usually fine but sometimes requires pinning if you're using more "niche" things like WDK)

tonymet  11 days ago

Nearly all of the Windows hate i see comes from 20 year old takes . ( the bing/cortana / copilot / ads slop criticism is warranted, but is also easily disabled).