@davesmits Can you file this an issue (dotnet/core is fine) asking for guidance, with more details? For example, I don't see a MongoDB dependency here: https://t.co/HdwHP0N9cq.
@Aaronontheweb@dddanielreis@lxztlr That book is likely still great as a complement to other materials. I have a signed copy! I suggest reading the docs in dotnet/runtime https://t.co/wMy8gO42V5
@shanselman@lakerfld We "syndicate" our README info to Docker Hub. That process is currently broken. It has been reported. Keep the reports coming. ty.
@shanselman@DonPwrShellHunt@code@lyrichardson01 All of our tags are multi-arch manifest-based, like `8.0`. However, the images underneath those tags are CPU-specific. We don't support QEMU for containers for x64 emulation on Arm64, but Rosetta may work.
@everybody_kurts Sorry for the delay. I haven't updated that post, but I updated another one with much the same info. I'll try to get to that other post next week.
https://t.co/hC2LB5I0a4
@dotMorten@Lucas_Trz Ubuntu and Red Hat, for example, only ship .1xx SDK builds, because they don't want breaking changes. We maintain .1xx until major version EOL because of that.
@dotMorten@Lucas_Trz The SDK "feature bands" align with VS dot releases and may have breaking changes. That's why we created the funky versioning scheme.
The diff between 200 and 201 is because there was some fix that had to go out immediately and there was no need to re-build the runtime.
@RickStrahl@KathleenDollard It sounds like you are regularly downloading runtime links, due to servicing. I was asking if a link that always provided the latest servicing update would help.