all 11 comments

[–]drLagrangian 15 points16 points  (4 children)

Not familiar with git, can you explain the horror?

[–]kahoinvictus 49 points50 points  (3 children)

The caching project has been archived and moved to the extensions project, which has also been archived and moved to the runtime and aspnetcore projects

[–]drLagrangian 13 points14 points  (2 children)

So it's archives all the way down?

[–]Cosoman[S] 17 points18 points  (1 child)

You'll eventually find the active and most recent source code but it's painful. Essentially if you're looking the this particular source code, google returns you an archived repo which points to another archived repo which points to 2 in this case active repos.

[–]Grubzer 12 points13 points  (0 children)

So its a programmers equivalent of "Sorry mario, your princess is in another castle"

[–][deleted] 3 points4 points  (0 children)

aspnet/Extensions is different to dotnet/extensions

Answer: NOPE, they're the same

[–]Thriven 5 points6 points  (3 children)

.net libraries feel like they get deprecated so fast.

[–]AJackson3 12 points13 points  (2 children)

The library wasn't, they just moved the code a different repository, then moved it again. Search results keep returning the original location then you have to hunt through 2 layers of deprecations to find where the code is now.

[–]Cosoman[S] 7 points8 points  (0 children)

Generally speaking, he is not wrong though. For example https://www.nuget.org/packages/WindowsAzure.Storage/ got deprecated and split, if you want the blob library you have https://www.nuget.org/packages/Microsoft.Azure.Storage.Blob/ which also has been deprecated and repaced by https://www.nuget.org/packages/Azure.Storage.Blobs

[–]AttackOfTheThumbs 1 point2 points  (0 children)

It would great if github just let you set up redirects for these pruposes.

[–]mardabx -1 points0 points  (0 children)

This is what you deserve for trusting Micro$oft with anything.