Interested in working in .NET Tooling? My team is hiring for a few roles. This is a great to impact the .NET ecosystem, work with devs all across Microsoft and help drive the .NET platform forward.
https://t.co/IcSLpDXPoS
https://t.co/lSxsm4pqxB
Hey #dotnet people! Exciting news! I've launched my YouTube channel: "Dissecting the Code".
It's going to be very similar to my blog, where I'll cover .NET internals, performance tips & tricks, and more deep dives. #csharp
I've already published the first two videos:
➡️ Episode 0: What You'll Learn Here
➡️ Episode 1: Dissecting Variable Lifetime
I hope you'll like it! Please share, subscribe, and let me know what you think! Your support means a lot to me. 🙏
Links to the channel & videos are 👇
@riosgeorge@davidfowl@GarethSeth A top priority of this effort is ensuring we have a smooth, and aesthetic, transition to a real project. Many of our design decisions come down to "okay, but how does that work once the customer transitions to a real project?"
Want to see what went down at Update Conference Prague? Watch the highlights and get ready for next year’s edition! 🎉
More than 40 sessions, top experts, and endless networking opportunities - online or in person.
✅ Save the date for next year: 13-14 Nov 2025!
🔗 https://t.co/ODKR0M6x4J
#UpdateConference #TechEvent #DeveloperLife #Networking #SoftwareDevelopment #Learning #TechConf @itixocz@riganti
@STeplyakov Definitely be interested to see if it caught any issues with us. Or honestly what docs you discovered that better outlined what is / isn't illegal. Getting to the "is this okay or not" has tripped us up a few timse
@Capyvara Correct. It's because the `Dispose` method mirrors the try / finally state from the main method. But it _only_ copies the finally blocks, nothing else. So the code between the finally blocks doesn't exist in Dispose
@dotMorten@timheuer The roslyn team is well aware of this bug because of the week of productivity lost to tracking it down when they introduced said marshalling bug into our own code base :)