C# 15 makes "unsafe" code better!
Curious what "unsafe" actually means, why it's useful, and what's changing?
We made a hands-on TUTORIAL where you can explore it all, EDITING and running C# 15 compiled to WebAssembly, right in your browser:
https://t.co/zN3VRHG606
Our email is also currently affected by today's global Outlook outage. Here's a meme to help us laugh despite the challenges:
"Technically, Jensen Huang is still CEO because they used Outlook to send his termination email this morning."
����
.NET 11 is here!
Fresh from the great #DotNetConf talks? Now's the time to try C# 15 yourself!
We built an online playground to learn, explore & experiment with the new features. No setup needed!
👉 https://t.co/cM6YnR8v47
Introducing 'Magic Animations" in XAML Designer!
The magic? Every animation smoothly transforms the entire app layout.
And if you give any two elements the same Magic Move ID, they'll morph & transition automatically, even across different control templates!
Free. No signup.
Try the animated card demo here (+ editable source code that opens in our online .NET IDE):
https://t.co/FTZhyF527k
Read the XAML animations library documentation (+ library source code, MIT-licensed):
https://t.co/6uZIPxse5S
Discover more animations and follow the tutorial in the Animations Gallery web app (use the menu on the left to navigate the 14 chapters):
https://t.co/wfrkUphRq4
What if .NET apps looked better than the rest?
Introducing the first XAML Designer where animations smoothly transform the entire app layout.
Try it yourself at https://t.co/J6FVLbOaLu. 100% free. No account needed.
Per element, not one global curve. Every animation takes its own Easing, right in the XAML:
<Border anim:Animate.Appear="{anim:Slide From=Bottom, Easing=Bouncy}"/>
<Button anim:Animate.MoveAndResize="{anim:Smooth Easing=EaseOut, Duration=0.4s}"/>
<Border anim:Animate.Hover="{anim:Lift Easing=Bouncy}"/>
Built-in curves: Smooth (the default), Gentle, Linear, Bouncy, EaseOut, EaseIn, EaseInOut, StrongEaseOut, StrongEaseIn, StrongEaseInOut and Overshoot. Bouncy and Overshoot take a Bounciness from 0.1 to 1.
For people coming from WPF or Silverlight: any IEasingFunction works too, like a CubicEase or an ElasticEase declared as a resource: Easing={StaticResource MyEase}
To reuse an effect, declare it once and use it everywhere, also in Styles:
<anim:Slide x:Key="Intro" From="Bottom" Easing="EaseOut" Duration="0.4s"/>
<Border anim:Animate.Appear="{StaticResource Intro}"/>
App-wide, AnimationSettings sets the default duration and the overall speed (Speed="2" plays everything twice as fast). It also respects the user's "reduce motion" setting automatically.
Full documentation: https://t.co/6uZIPxse5S
Introducing OpenSilver UI Animations!
We think it's one of the coolest UI animation libraries in .NET.
Add one XAML attribute and elements smoothly animate as layouts change.
No storyboards. No code-behind. No app logic changes.
Live demos, docs & source (MIT) in the reply👇
Not directly, unfortunately.
The trick is that OpenSilver has two separate trees: the XAML visual tree and the HTML DOM used for rendering.
When the layout changes, we let the XAML side jump straight to its final state, and animate the DOM separately. So from the app's point of view, everything is already in its final position and size. No RenderTransforms or dependency properties are touched.
This also lets us do things that would be quite tricky in regular WPF, like animating an element after it's been removed from the visual tree, or smoothly resizing a button when its text changes.
For WPF, though, check out @XamlFlair: it's a really nice library that covers some of the same ground.
And soon, you’ll be able to create these animations visually with our XAML Designer, right inside Visual Studio, VS Code, or online at https://t.co/J6FVLbOaLu
Stay tuned! 👀