Displaying episodes 31 - 60 of 63 in total
Microsoft patches a nasty CVE with System.Text.Encodings.Web that affects every .NET platform (except maybe framework?); Microsoft takes down a security researcher's PoC of the Exchange hack, and "static abstract" may become a thing in C#.
Exchange gets hacked; Microsoft .NET Foundation is opening up (hhehehe) about its "assignment model" change.
Maoni Stephens (writer of the Pinned Object Heap Blog post and Garbage Collector Guru at Microsoft) gets a promotion.
Microsoft releases "Dapr", in a homophonic 'homage' to Dapper.
Microsoft Shares your Info with Canonical if you use Ubuntu; .NET Turns 19; and three CVEs get patched in the .NET World.
Microsoft defers 2022 Election Cycle contributions to congressional representatives that supported the objections to certification of electors on January 6th. Microsoft Ignite is coming and it's free.
The .NET team axes their backlog in vain hopes of managing it. Microsoft releases LAMBDA; an excel function that will likely power AI well into the next decade.
Microsoft spills why they make Political Action Committee Contributions to members of congress that supported the insurrection on January 6th; Visual Studio now supports preprocessor symbols for intellisense; and two conferences are coming up.
Nuget can run arbitrary code on your system; Parler's woes get worse (yay!); and Khalid A. shares inspirational quotes from artists that apply to programming. Oh yea, Microsoft releases new .NET Core updates that fix a major CVE.
A Capitol Insurrection; JetBrains refutes the NYT tying it to the Solarwinds Hack, and Serverless.com makes a major security "oopsie".
Solarwinds got hacked; and dozens of US Government Agencies were infiltrated. Microsoft navel-gazes into its eco-system problems; and there's a little bit of "If it's good for Apple it's good for us" going on too.
A nasty RCE has been patched; .NET 5.0.1 has been released; and there's a new site that lets you find blogs for any tech stack.
December 6th was the 31st anniversary of the École Polytechnique massacre; we dive into some Microservices tools and framework improvements in .NET 5; and Windows Terminal may get... Stories?
Microsoft now spies on your productivity in O365; lots of helpful packages abound this week around tough problems; and everyone is hung over from too much turkey.
Helpful tips if you want to build .NET 5 applications; a new fuzzer; and the galaxy brain meme comes to C#
.NET 5 is released; VB.NET is... stable, and the hipster C# (F#) gets some updates.
Entity Framework Core team probably isn't sleeping, .NET 5 Drops tomorrow, and hardcoded special characters will be the death of us all.
We dive deeper into the non-bug bug around String comparison and globalization; and we wait patiently for .NET 5 to drop.
There's a b^H^H I mean feature with string.IndexOf in .NET 5, and there exists at least one person out there combining Blazor with ABAC. In a way, we're all stronger through this adversity. I think.
Microsoft fixes 87 security bugs, countless CVEs, and reminds us they have money to spend, just not on non-Microsoft Open Source Projects.
Glaring bug with MARS (Multiple Active Result Sets) on EF / SqlClient for Linux on .NET Core; and a whole bunch of stuff that's less bad. Except for the Labor Dept.'s bonehead move.
Two Conferences walked into a bar, one named .NET Conf and one named dotnetconf. Confusion ensues.
A special magic string that can destroy systems that save your passwords in plain text, and we're partying like it's 1999 because up is down, and Code Project is back.
.NET 5 RC 1 is released; and the .NET community learns an uncomfortable truth: People would rather learn node than learn .NET.
Two major CVEs in the wild, one patched; EF Core gained some quarantine weight, but I'm not one to judge. I eat junk food, and EF Core adds features. We all deal with these "unprecedented times" in our own way.
.NET 5 Preview 8 is out; and a blog post asks: is blazor the future of development?
Microsoft waits 2 years to patch an exploit in the wild, and other news from last week.
Microsoft releases updates to all its .NET ecosystem tooling to account for another big CVE; Microsoft humble-brags about OSS.
Microsoft reminds everyone that Ignite is coming; .NET Core refuses to be built.
Stack Overflow releases its performance metrics; Hacker News Cries. The .NET foundation released its "State of the Foundation" report, and I go deep into what the .NET foundation is, who it's for, and I ask the question: Are they the interest group we need them to be?