Anyone know how I can see the actual thrown exception in Rider? I got the exception in "Threads & Locals" under "$exception", but I was expecting a nicer view in the "Unhandled exception" window. Is that configurable somehow?
@robertpi The OSS ecosystem is hella-strong compared to any other ecosystem I’ve seen.
If you want to slap an app together, you can find the building block easily.
#dotnet, on the other hand, is missing a lot of integrations with macOS and Linux that become very clear quickly. For example, try accessing a video camera or microphone from a .NET application in a cross-platform way.
Instead of Google Ads, I should sell ad space directly on individual blog posts. It would probably net me more in the long run. It would also be less intrusive.
@breakpointshow Great show! It would be cool if you made this „something cool about #dotnet we‘ve seen, read, discovered, used lately“ a permanent part of the show.
Start or end the show with it and give it catchy name.
Do you like #FediBuzz and would love for it to continue? I know, I'm in the same camp as you.
@astro made it possible for you to donate a token, and the page says
> We consume only the federated timeline. We don't even see boosts or replies. The permissions that we request shouldn't allow us to do anything else.
Unfortunately, that's misleading. I agree that the permissions “shouldn't allow them to do anything else", but the reality is that today, they do.
The token you're donating can read the private messages of the user that created the token.
So if you do so, make sure you trust @astro with access to your private messages and their ability to keep your token secure or create a token from an account where you don't have private messages.
If you regret donating the token, you can revoke it at /oauth/authorized_applications
I don't like the way #Mastodon devs are downplaying the importance that #FediBuzz has on small instances... but asking for tokens that can read private messages without disclosing it is wrong. And considering that the people that are aware of it are mostly admins, means that it's more likely they will have important messages on their accounts.
My take is that the community’s response to Moq would have been absolutely justified had there been actual malicious intent by an adversary.
Knowing Kzu I can attest that there was absolutely no such intent, and he has always deeply cared for the ecosystem. The value delivered by Moq is immense. We grabbed our pitchforks too soon and a civil discussion needs to be had first. He doesn’t deserve being treated like this.
"bflat is a native compiler for C# that comes with everything you need to build C# apps for any of the supported platforms. No additional SDKs or NDKs needed"
With it, it's even possible to build C# applications to #Windows 3.1 (!?)
Author: Michal Strehovský - "I work remotely at the .NET Runtime team at Microsoft."
@nick_tune@dgoemans I think they have their advantages. If we’re talking about #dotnet, I think EF Core has been a real success story where the focus on performance has it neck-and-neck with Micro-ORMs.
That said, I don’t think it’s as simple as being on team ORM or Artisanal SQL.
The move to feedz.io is complete. Note that only new package builds will go here; if you're currently using the MyGet feed for prerelease packages, please ONLY update to feedz.io when you're ready to take newer dependencies.
While I appreciate what pre-commit hooks can do, they add overhead that I’m not sure is worth it for me in the long run.
If you’re looking at adding #ReSharper CLI as a pre-commit action to all #dotnet environments, here are the files for Husky.NET: task-runner.json and resharper-cli.csx (you’ll need to install the ReSharper CLI tools).
#dotnet could simplify executing this suggestion in the error message by concatenating the workloads into one statement rather than listing each out like this.
Using Moq in a lot of projects at work. I'm gonna wait this out a bit before I start changing it out to anything else, but this isn't nice to see.
A lot of damage is being done there.
Could novice programmers write clean code from the start?
Clean code is not just for professional developers. Especially beginners quickly lose track of their code. Clean code would help against that. I think we can explain clean code principles to absolute programming beginners, for example the DRY principle:
Few people on the planet this is useful for, but here’s a #RoslynAnalyzer for when you have VB legacy code and want compiler warnings if it had Option Strict Off: