Bastian Schmidt

@mkristensen One of the recent updates uninstalled/replaced my already installed 10.0.201 x64 SDK with 10.0.202 x64 SDK "from Visual Studio". We played the game "VS dictates versions" ages ago... Could VS just stop uninstalling/replacing stuff it doesn't own?

Friday question: What issue with Visual Studio 2026 did you run into this week, that would make you happy to see fixed?

@Dave_DotNet There are way more important things to fix in the language instead of this abomination. How are we supposed to give feedback if the proposal issue is locked?

Target-typed static member lookup in C# #dotnet This feature enables a type name to be omitted from static member access when it is the same as the target type. It's currently a champion issue (link below). Would you like to see it in C#?

Just released Fluent.Ribbon 11.0 🎉 #OSS #FluentRibbon #WPF #XAML #Dotnet github.com/fluentribbon/F…

Version 7.0.0 of #ControlzEx has been released. github.com/ControlzEx/Con… #MahApps #FluentRibbon #OSS #FOSS #XAML #WPF #dotnet #NET

@dotMorten @PunkChaurasia While using StaticResource? Never when it's already created. If you want it to update live you must use DynamicResource. If your background is based on a color from the theme you also have to use DynamicResource when using the color.

@PunkChaurasia Do you know? How would I make this button update when the theme changes? <Button Background="{StaticResource MyButtonBackground}" />

Can someone explain how to use the new ThemeMode in #WPF for my own styles? Looks like if you do any sort of style override, the feature causes more problems than it solves :-( #dotnetconf

Time again to call out #MahApps and #controlzEx for the nice UI tools that make it possible for me to build nice looking and functional UIs. Thanks for the work you've put into this @punker76, @batzendev and all contribs for MahApps!

The #IconPacks v5 has just been released. ❤️🎉🤘 Get many updated and also new #Icons packs from ❤️ Take it, use it, love it and give a ⭐ to all the #Icon libs! github.com/MahApps/MahApp… #OSS #MahApps #XAML #Material #WPF #UWP #AvaloniaUI #netcore #dotnet #net6 #MVPBuzz

Do you know that @batzendev does a really awesome job with our custom #ControlzEx window chrome solution? Not, then give him a star, a like or whatever ❤️🤘 #MahApps #OSS #MVPBuzz #FluentRibbon #XAML

@kzu It's not working around per se. I have that filter turned off by default, for example.

@batzendev I'm fine if folks want to workaround rather than support me. Otherwise, I wouldn't even opensource things in the first place.

How would folks feel if an OSS API was usable/available (in intellisense) only while you're sponsoring (or during a trial period)? Like Adobe creative cloud, which you pay only when you actually need to use it. The rest of the time, the code would compile just fine, only w/o intellisense 🤔 (just as the assets you created with Adobe don't just stop functioning when you pause the subscription). Think everything becomes EditorBrowsable.Never. And obviously an org could sponsor and every member of the org gets full intellisense.

@robert0muehsig @ChristophToh @lxztlr Fachsoftware gibt's halt nicht als OSS und auch eher selten unter Linux. Hat auch bei uns, soweit ich weiß, noch kein Kunde gefordert das unsere Software unter Linux laufen soll. Selbst wenn bräuchte das etliche Jahre bis das da läuft.

@ChristophToh @lxztlr Also ich bin natürlich voreingenommen, da wir rund um Office unser Produkt gebaut haben und da sind wir ja nicht alleine. Jetzt kann man sagen: Einer muss ja anfangen, aber auf der Ebene ist das ein Himmelfahrtskommando, weil alle anderen Office einsetzen samt Toolings.

@nuget @aristurtledev That gap should have been closed before you spammed countless repositories with issues requesting the creation of a separate readme...

@aristurtledev You shouldn't have to. We are working on making this experience seamless and bridging the parity gap. Hopefully some good news soon.

Hi @nuget, could the HTML in the README markdown files maybe be used on the NuGet page? I really don't want to maintain two README's per project (one for GitHub and one for NuGet) just so I can center a banner and include other info. NuGet (left) vs GitHub (right)

@DevLeaderCa We used to use MEF. But assembly scanning was horribly slow. So we moved to DryIOC, but kept the MEF strategy of not having to register manually. To get rid of the assembly scanning cost we add assembly level attributes through PostSharp during compile and scan those. Way faster.

What's your strategy for managing dependency injection in .NET Core projects?

@GeertvanHorrik Wait for the next one (v11) where you get support for Mica backdrop etc.. At least on Win11. 😁

Just released Fluent.Ribbon 10.1 🎉 #OSS #FluentRibbon #WPF #XAML #Dotnet GitHub: github.com/fluentribbon/F… NuGet: nuget.org/packages/Fluen…

@SimonCropp @neuecc Sent you the link via DM.

Utf8StreamReader v1.2.0 is now available! The FileStream handling method has been fine-tuned, allowing for incredibly fast data reading from files! Properly handling FileStream can be challenging. Detailed information is provided in the ReadMe. github.com/Cysharp/Utf8St…

@neuecc The code is part of my private app framework which is not OSS. But i would be happy to chat about it with you and show it. Maybe you have some ideas on how to make both of our solutions faster. Will send you a DM.

@batzendev Good! Where is code?

@robert0muehsig @davidfowl AOT doesn't require a .NET runtime. It's totally self contained, as far as i know.

@batzendev @davidfowl TBH: No clue, but I check some GitHub issues from time to time and it seems complicated (multiple .NET runtimes in one process, WinForm Message loop, etc.)

We have an internal forum where teams come and share experiences migrating from .NET Framework to modern .NET. Every week there are talks from teams moving their applications. Lots of very cool sharing of techniques to migrate and experiences (both positive and negative) #dotnet

@robert0muehsig @davidfowl Shouldn't it be possible to AOT compile your addins?

@davidfowl Part of our application is stuck on .NET framework because of Office COM addins. The sad part is, that some „shared“ code is using .NET Standard 2.0 (so we can link the same components from .NET framework and .Net 8), but some packages start to dismiss .Net standard. :-/