home.social

#nuget — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nuget, aggregated by home.social.

fetched live
  1. I don't develop using #npm, and I guess this happens with #pypi and #nuget as well.
    What's the answer? Only install stuff completely manually? Don't store credentials on your dev PCs, only in your e.g. smartphone and enter them manually? Let humans manually verify each upload to package registries? /s

  2. I don't develop using #npm, and I guess this happens with #pypi and #nuget as well.
    What's the answer? Only install stuff completely manually? Don't store credentials on your dev PCs, only in your e.g. smartphone and enter them manually? Let humans manually verify each upload to package registries? /s

  3. I don't develop using #npm, and I guess this happens with #pypi and #nuget as well.
    What's the answer? Only install stuff completely manually? Don't store credentials on your dev PCs, only in your e.g. smartphone and enter them manually? Let humans manually verify each upload to package registries? /s

  4. I don't develop using #npm, and I guess this happens with #pypi and #nuget as well.
    What's the answer? Only install stuff completely manually? Don't store credentials on your dev PCs, only in your e.g. smartphone and enter them manually? Let humans manually verify each upload to package registries? /s

  5. From the .NET blog...

    In case you missed it earlier...

    Strengthening NuGet Supply Chain Security: Reducing API Key Lifetime
    devblogs.microsoft.com/dotnet/

  6. From the .NET blog...

    In case you missed it earlier...

    Strengthening NuGet Supply Chain Security: Reducing API Key Lifetime
    devblogs.microsoft.com/dotnet/ #dotnet #NuGet #Security

  7. From the .NET blog...

    In case you missed it earlier...

    Strengthening NuGet Supply Chain Security: Reducing API Key Lifetime
    devblogs.microsoft.com/dotnet/ #dotnet #NuGet #Security

  8. From the .NET blog...

    In case you missed it earlier...

    Strengthening NuGet Supply Chain Security: Reducing API Key Lifetime
    devblogs.microsoft.com/dotnet/ #dotnet #NuGet #Security

  9. From the .NET blog...

    In case you missed it earlier...

    Strengthening NuGet Supply Chain Security: Reducing API Key Lifetime
    devblogs.microsoft.com/dotnet/ #dotnet #NuGet #Security

  10. Как я посадил WireMock.Net на gRPC стероиды

    WireMock.Net умеет мокать gRPC . Но для этого он заставляет разработчика таскать .proto файлы и поддерживать лишнюю конфигурацию. Я контрибьютил в проект несколько месяцев, разобрался в кишках и написал своё расширение WireMock.Grpc.Protobuf Пакет предлагает gRPC моки через типизированные контракты Google.Protobuf . Получилось короче, надёжнее и заметно удобнее. В статье покажу, почему мой способ удобнее стандартного, как всё устроено под капотом и зачем вашему проекту пакет WireMock.Grpc.Protobuf Кстати, подобные инженерные разборы, open-source и внутренности .NET я регулярно публикую в Telegram-канале StepOne . Если статья зайдёт — заглядывайте. dotnet add package WireMock.Grpc.Protobuf

    habr.com/ru/articles/1063162/

    #grpc #proto #protobuf #wiremock #google #csharp #dotnet #nuget #github #mock

  11. Как я посадил WireMock.Net на gRPC стероиды

    WireMock.Net умеет мокать gRPC . Но для этого он заставляет разработчика таскать .proto файлы и поддерживать лишнюю конфигурацию. Я контрибьютил в проект несколько месяцев, разобрался в кишках и написал своё расширение WireMock.Grpc.Protobuf Пакет предлагает gRPC моки через типизированные контракты Google.Protobuf . Получилось короче, надёжнее и заметно удобнее. В статье покажу, почему мой способ удобнее стандартного, как всё устроено под капотом и зачем вашему проекту пакет WireMock.Grpc.Protobuf Кстати, подобные инженерные разборы, open-source и внутренности .NET я регулярно публикую в Telegram-канале StepOne . Если статья зайдёт — заглядывайте. dotnet add package WireMock.Grpc.Protobuf

    habr.com/ru/articles/1063162/

    #grpc #proto #protobuf #wiremock #google #csharp #dotnet #nuget #github #mock

  12. Как я посадил WireMock.Net на gRPC стероиды

    WireMock.Net умеет мокать gRPC . Но для этого он заставляет разработчика таскать .proto файлы и поддерживать лишнюю конфигурацию. Я контрибьютил в проект несколько месяцев, разобрался в кишках и написал своё расширение WireMock.Grpc.Protobuf Пакет предлагает gRPC моки через типизированные контракты Google.Protobuf . Получилось короче, надёжнее и заметно удобнее. В статье покажу, почему мой способ удобнее стандартного, как всё устроено под капотом и зачем вашему проекту пакет WireMock.Grpc.Protobuf Кстати, подобные инженерные разборы, open-source и внутренности .NET я регулярно публикую в Telegram-канале StepOne . Если статья зайдёт — заглядывайте. dotnet add package WireMock.Grpc.Protobuf

    habr.com/ru/articles/1063162/

    #grpc #proto #protobuf #wiremock #google #csharp #dotnet #nuget #github #mock

  13. I just released version 0.9 of ConsoleRenderer!

    This version increases performance for sparsely populated screens by a significant margin, thanks to @micutio!

    This version also drops support for .NET 8 in favor of .NET 10, which is the latest LTS version.

    The previous version is still very stable, so if you you depend on ConsoleRenderer and haven't moved your project to .NET 10, you can still use that without issue.

    nuget.org/packages/ConsoleRend

    #nuget #rendering #terminal #foss

  14. I just released version 0.9 of ConsoleRenderer!

    This version increases performance for sparsely populated screens by a significant margin, thanks to @micutio!

    This version also drops support for .NET 8 in favor of .NET 10, which is the latest LTS version.

    The previous version is still very stable, so if you you depend on ConsoleRenderer and haven't moved your project to .NET 10, you can still use that without issue.

    nuget.org/packages/ConsoleRend

  15. I just released version 0.9 of ConsoleRenderer!

    This version increases performance for sparsely populated screens by a significant margin, thanks to @micutio!

    This version also drops support for .NET 8 in favor of .NET 10, which is the latest LTS version.

    The previous version is still very stable, so if you you depend on ConsoleRenderer and haven't moved your project to .NET 10, you can still use that without issue.

    nuget.org/packages/ConsoleRend

    #nuget #rendering #terminal #foss

  16. I just released version 0.9 of ConsoleRenderer!

    This version increases performance for sparsely populated screens by a significant margin, thanks to @micutio!

    This version also drops support for .NET 8 in favor of .NET 10, which is the latest LTS version.

    The previous version is still very stable, so if you you depend on ConsoleRenderer and haven't moved your project to .NET 10, you can still use that without issue.

    nuget.org/packages/ConsoleRend

    #nuget #rendering #terminal #foss

  17. I just released version 0.9 of ConsoleRenderer!

    This version increases performance for sparsely populated screens by a significant margin, thanks to @micutio!

    This version also drops support for .NET 8 in favor of .NET 10, which is the latest LTS version.

    The previous version is still very stable, so if you you depend on ConsoleRenderer and haven't moved your project to .NET 10, you can still use that without issue.

    nuget.org/packages/ConsoleRend

    #nuget #rendering #terminal #foss

  18. If you're a C# #developer and need some helpful generalized/reusable code, you can check out an offshoot of my big project called #CapyKit.

    git.jordanwages.com/wagesj45/C

    Documentation: capykit.happycapy.net/

    Available in #nuget via #selfhosted #Foregejo repository. Or build it yourself.

  19. If you're a C# #developer and need some helpful generalized/reusable code, you can check out an offshoot of my big project called #CapyKit.

    git.jordanwages.com/wagesj45/C

    Documentation: capykit.happycapy.net/

    Available in #nuget via #selfhosted #Foregejo repository. Or build it yourself.

  20. If you're a C# #developer and need some helpful generalized/reusable code, you can check out an offshoot of my big project called #CapyKit.

    git.jordanwages.com/wagesj45/C

    Documentation: capykit.happycapy.net/

    Available in #nuget via #selfhosted #Foregejo repository. Or build it yourself.

  21. If you're a C# #developer and need some helpful generalized/reusable code, you can check out an offshoot of my big project called #CapyKit.

    git.jordanwages.com/wagesj45/C

    Documentation: capykit.happycapy.net/

    Available in #nuget via #selfhosted #Foregejo repository. Or build it yourself.

  22. #TIL Nowadays #NuGET replaces #API keys with what they call trusted publishing which is kind of oAuth where CI runs (currently only #GitHub actions, it seems) ask for a short-lived token, receive it and publish a package. Reason number 42 for me to stay on gitHub. #DotNet

  23. #TIL Nowadays #NuGET replaces #API keys with what they call trusted publishing which is kind of oAuth where CI runs (currently only #GitHub actions, it seems) ask for a short-lived token, receive it and publish a package. Reason number 42 for me to stay on gitHub. #DotNet

  24. #TIL Nowadays #NuGET replaces #API keys with what they call trusted publishing which is kind of oAuth where CI runs (currently only #GitHub actions, it seems) ask for a short-lived token, receive it and publish a package. Reason number 42 for me to stay on gitHub. #DotNet

  25. #TIL Nowadays #NuGET replaces #API keys with what they call trusted publishing which is kind of oAuth where CI runs (currently only #GitHub actions, it seems) ask for a short-lived token, receive it and publish a package. Reason number 42 for me to stay on gitHub. #DotNet

  26. #TIL Nowadays #NuGET replaces #API keys with what they call trusted publishing which is kind of oAuth where CI runs (currently only #GitHub actions, it seems) ask for a short-lived token, receive it and publish a package. Reason number 42 for me to stay on gitHub. #DotNet

  27. Just blogged: Follow-up to my 2021 console stack post: templates scaffold well, but shared glue code drifts when you maintain many CLI tools.

    Now I use Devlead.Console.Template plus the Devlead.Console source package. Scaffold once, update bootstrap via NuGet. Partial Program hooks for your commands and DI.

    devlead.se/posts/2026/2026-06-

    #dotnet #csharp #oss #nuget

  28. Just blogged: Follow-up to my 2021 console stack post: templates scaffold well, but shared glue code drifts when you maintain many CLI tools.

    Now I use Devlead.Console.Template plus the Devlead.Console source package. Scaffold once, update bootstrap via NuGet. Partial Program hooks for your commands and DI.

    devlead.se/posts/2026/2026-06-

    #dotnet #csharp #oss #nuget

  29. Just blogged: Follow-up to my 2021 console stack post: templates scaffold well, but shared glue code drifts when you maintain many CLI tools.

    Now I use Devlead.Console.Template plus the Devlead.Console source package. Scaffold once, update bootstrap via NuGet. Partial Program hooks for your commands and DI.

    devlead.se/posts/2026/2026-06-

    #dotnet #csharp #oss #nuget

  30. Just blogged: Follow-up to my 2021 console stack post: templates scaffold well, but shared glue code drifts when you maintain many CLI tools.

    Now I use Devlead.Console.Template plus the Devlead.Console source package. Scaffold once, update bootstrap via NuGet. Partial Program hooks for your commands and DI.

    devlead.se/posts/2026/2026-06-

    #dotnet #csharp #oss #nuget