Tweetovi

Blokirali ste korisnika/cu @torn_hoof

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @torn_hoof

  1. proslijedio/la je Tweet
    21. sij

    Your re-sleeving is now complete. 2.27.20.

    Poništi
  2. proslijedio/la je Tweet
    10. sij

    Where does the hurting stop? Microsoft postponing necessary features that require other DI Container to integrate with ASPNET Core:

    Poništi
  3. proslijedio/la je Tweet
    7. sij

    I put together a longer form of my thoughts from yesterday on .NET Core, .NET 5, and speculation on F/OSS on the older .NET Framework:

    Poništi
  4. proslijedio/la je Tweet
    13. pro 2019.
    Poništi
  5. proslijedio/la je Tweet
    2. pro 2019.
    Odgovor korisnicima

    Yes, as long as your test methods are async Task. If they're async void, then different test frameworks have wildly different behavior. Summary: always use async Task for unit tests and make sure your testing framework is relatively up-to-date, and you should be good!

    Poništi
  6. proslijedio/la je Tweet

    Good news everyone! I'm looking for a job, I've been let go due to a re-organization. Anyone interested in a .NET or Ruby developer that has decent security chops? Washington DC or preferably remote. DMs open.

    Prikaži ovu nit
    Poništi
  7. proslijedio/la je Tweet
    14. stu 2019.

    Just blogged: High-Performance Logging in .NET Core. An exploration (with benchmarks) of reducing logging allocations by applying the LoggerMessage pattern in and .

    Poništi
  8. proslijedio/la je Tweet
    5. stu 2019.

    If you use BinaryFormatter in your .NET code, STOP WHAT YOU'RE DOING AND WATCH THIS. Then move to a different serializer.

    Poništi
  9. proslijedio/la je Tweet
    24. lis 2019.

    If you are using BenchmarkDotNet and .NET Core 3.0+ then you MUST update to the latest version. Otherwise, the allocated memory reported by MemoryDiagnoser is per single thread, not all of them.

    Prikaži ovu nit
    Poništi
  10. proslijedio/la je Tweet
    24. lis 2019.

    v0.12.0 has been released! .NET Core 3.1/.NET Framework 4.8 support, command-line templates, NativeMemoryProfiler, ThreadingDiagnoser, LINQPad 6 support, fast documentation search, and tons of other improvements!

    Poništi
  11. proslijedio/la je Tweet

    On how you can react to the chrome changes. Upcoming SameSite Cookie Changes in and Core

    Prikaži ovu nit
    Poništi
  12. proslijedio/la je Tweet
    17. lis 2019.

    For those who have experienced missing method exceptions when moving to EF Core 3.0, an updated version of OpenIddict 2.x is now available:

    Poništi
  13. proslijedio/la je Tweet
    11. lis 2019.

    Blogged: "Distribution comparison via the shift and ratio functions"

    Poništi
  14. proslijedio/la je Tweet
    7. lis 2019.

    Blogged: "An implementation of ED-PELT algorithm for efficient changepoint detection"

    Poništi
  15. proslijedio/la je Tweet

    Based on feedback from the .NET community; please read my statement: "Rethinking Project Maturity as a Community Process"

    Poništi
  16. proslijedio/la je Tweet

    When we watch TV, our TVs watch us back and track our habits. This practice has exploded recently since it hasn’t faced much public scrutiny. But in the last few days, not one but *three* papers have dropped that uncover the extent of tracking on TVs. Let me tell you about them.

    Prikaži ovu nit
    Poništi
  17. proslijedio/la je Tweet
    25. ruj 2019.
    Odgovor korisnicima i sljedećem broju korisnika:

    it's designed to be viral and will bring similar issues to .NET OSS as strong naming.

    Poništi
  18. proslijedio/la je Tweet

    Time to make some 3.0 non-preview packages!

    Prikaži ovu nit
    Poništi
  19. proslijedio/la je Tweet
    11. ruj 2019.
    Poništi
  20. proslijedio/la je Tweet
    6. ruj 2019.
    Odgovor korisnicima i sljedećem broju korisnika:

    Here's how I do an enum->ulong conversion in ZeroLog: This uses InlineIL, and doesn't even feel wrong 😉

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·