home.social

#nuget — Public Fediverse posts

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

fetched live
  1. At work we have five different environment variables for specifying the GitHub token for the same NuGet package source. And both per-repository NuGet.Config and machine-wide NuGet.Config for this source. A long history of teams not communicating is my guess.

    I digged through all configurations to discover this, but we should really consolidate... Well, at least I now have a wrapper for dotnet which sets these variables to avoid biting me when I cross team boundaries.

    #dotnet #nuget

  2. At work we have five different environment variables for specifying the GitHub token for the same NuGet package source. And both per-repository NuGet.Config and machine-wide NuGet.Config for this source. A long history of teams not communicating is my guess.

    I digged through all configurations to discover this, but we should really consolidate... Well, at least I now have a wrapper for dotnet which sets these variables to avoid biting me when I cross team boundaries.

  3. At work we have five different environment variables for specifying the GitHub token for the same NuGet package source. And both per-repository NuGet.Config and machine-wide NuGet.Config for this source. A long history of teams not communicating is my guess.

    I digged through all configurations to discover this, but we should really consolidate... Well, at least I now have a wrapper for dotnet which sets these variables to avoid biting me when I cross team boundaries.

    #dotnet #nuget

  4. At work we have five different environment variables for specifying the GitHub token for the same NuGet package source. And both per-repository NuGet.Config and machine-wide NuGet.Config for this source. A long history of teams not communicating is my guess.

    I digged through all configurations to discover this, but we should really consolidate... Well, at least I now have a wrapper for dotnet which sets these variables to avoid biting me when I cross team boundaries.

    #dotnet #nuget

  5. At work we have five different environment variables for specifying the GitHub token for the same NuGet package source. And both per-repository NuGet.Config and machine-wide NuGet.Config for this source. A long history of teams not communicating is my guess.

    I digged through all configurations to discover this, but we should really consolidate... Well, at least I now have a wrapper for dotnet which sets these variables to avoid biting me when I cross team boundaries.

    #dotnet #nuget

  6. 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

  7. 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

  8. 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

  9. 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

  10. From the .NET blog...

    In case you missed it earlier...

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

  11. 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

  12. 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

  13. 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

  14. 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

  15. Как я посадил 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

  16. Как я посадил 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

  17. Как я посадил 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

  18. 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

  19. 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

  20. 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

  21. 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

  22. 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

  23. 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.

  24. 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.

  25. 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.

  26. 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.