Once upon a time, a content management system for microsoft.com was a plug in for VS. And also a plug in for Word. And these two plugins had different feature sets, so you had to use both to manage content on microsoft.com. Don't ask how I know.

[–] Lmaydev@programming.dev 3 points 1 year ago

It's not so bad in the newer version. The switch x64 and put of process architecture helps a decent amount.

I always have a pretty beefy dev machine though.

[–] blackstrat@lemmy.fwgx.uk 3 points 1 year ago (1 children)

Can confirm. Have had to download the full VS 2022 Pro over a shit wifi connection at work 55GB. It took half a day then failed. Re run the command to recheck every package and get the missing / broken ones and it is a single threaded app so it takes forever computing file hashes on one thread.

In the end it took around 7.5 hours.

[–] PixxlMan@lemmy.world 1 points 1 year ago (1 children)

What workloads did you download fit it to be that big?

[–] blackstrat@lemmy.fwgx.uk 2 points 1 year ago (1 children)

Everything. It's going on a network not connected to the internet so I don't want to exclude something and have go through the faff of getting extra bits that end up being needed.

[–] PixxlMan@lemmy.world 1 points 1 year ago

Fair enough! Not terribly surprised about the size then, though - there's a lot of stuff VS can do. When limited to just a few workloads you need the size isn't unreasonable in my opinion though.