@jonskeet I asked this question to an NICU night-shift nurse once! Apparently working the night of the time-shift really messes with record-keeping since (unsurprisingly?) medical software is not programmed to handle it! e.g. taking an hourly measurement "twice" in an hour
Interested in tackling large scale projects like this one to improve the .NET developer experience at Mastercard?
Come work with me! DMs open if you have questions.
https://t.co/4ahSnKJwpX
This blog post is for those of you who were interested for practical details about how my team automated the .NET Core migration.
P.S. In very related news, my #dotnetconf talk is now on YouTube!
https://t.co/S56JOxmivM
@KirillOsenkov Thanks for the note! I've updated the footer.
P.S. I've been profiling build times trying to improve performance from a fresh clone, and https://t.co/Gc8W5y7aHq has been so helpful in deciding where to invest!
Blogged: "Learn MSBuild" (a 4-part series)
Alternate title: "MSBuild is really just C# with more angle brackets"
Start with my favorite:
https://t.co/IKqL2Mis8I
#MSBuild
Blogged: "How to fix "resolve operation has already ended" exceptions in lambda Autofac registrations"
Alternate title: "Come for the bugfix, stay for the extended discussion of @AutofacIoC concurrency internals"😀
https://t.co/p7JQupyLqz
This blog post is for those of you who were interested for practical details about how my team automated the .NET Core migration.
P.S. In very related news, my #dotnetconf talk is now on YouTube!
https://t.co/S56JOxmivM
Blogged: "Refactor C# code with the Roslyn Syntax API"
Alternate title: "Write scripts that make everyone in your organization feel like a wizard."
https://t.co/rLbqPvXm7k
@thematthewarp Good catch! There isn't a strict dependency between the two, we could have done them in either order.
Reason: By waiting, we had a stronger grasp of which internal packages were not made "obsolete" by https://t.co/urpd9IWO5n Core, i.e. which needed to be .NET Standard.
@skotekar_ None of our applications used Webforms. I don't envy the challenge of migrating Webforms, though the alternatives (Blazor and Razor Pages) do seem to be getting easier to use and more feature-ful with every release.
@SinanHana Near the beginning, we tried out a neat but ultimately insufficient NUnit 2 -> 3 migration tool, so we wrote our own.
To minimize the effort for product teams, we preferred writing custom scripts doing 95% of the work over an off-the-shelf tools doing 80%.
@vaclavpekarek Thanks for the kind words Václav!
Unfortunately since Web Forms is not supported outside of .NET Framework, you would need to migrate to Blazor / Razor Pages after getting to https://t.co/urpd9IWO5n Core but before on .NET Core.
@MicbOliver Thanks for the kind words Mark!
Unfortunately .NET 5 is not a Long Term Support (LTS) release, so it isn't a great choice for our large ecosystem. Don't worry, we'll be back on the bandwagon for .NET 6 (which is LTS)!
https://t.co/q8ZMUZybRl
@jpazniokas This is fascinating! At work, 100% of us pronounce https://t.co/urpd9IWO5n as two syllables. I like the efficiency of it, reminds me of SQL vs. S Q L.
Honored to be speaking at .NET Conf this year!
My session "2 years, 200 applications: A .NET Core Migration at Enterprise Scale" is about two things I love -- solving complex problems with common code solutions and empowering others. ❤️
#dotnetconf
The agenda is out! See what's happening the world of .NET.
#dotNETConf is coming November 10 — 12 2020
Come celebrate the new .NET Core 5.0 launch 🚀 with us. We might even have a very special guest for you, too! 😁
Make sure to add it to your calendar: https://t.co/CqGPPxi9kH
Just published an "An Illustrated Guide to @AutofacIoC"!
Did I maybe go overboard with all the food analogies?
Yes.
Did I have so, so much fun thinking of these food analogies?
Also yes.
https://t.co/HqlJCYTZON
Blogged about a funky #MSBuild thing we did on my team recently. Another example of "write the blog post you wanted to see in the world".
https://t.co/fRQ7svudVl