I’m regenerating these #Nuget keys in _literally_ the final hour

How on earth do people overcome the feeling of *itching to develop that #NuGet package but cba to maintain it*

I've just released a new #dotnet #nuget package called "FastLogr".

Short summary: IMHO better approach at high performance logging that tackle the warning "CA1848: Use the LoggerMessage delegates"

Would appreciate some honest feedback, no matter if pro and/or con.

https://www.nuget.org/packages/FastLogr/

https://github.com/MichaelHochriegl/FastLogr

The rule is simple: If you don't know how to update #nuget packages, do not update them.

Holy moly!

647,000+ downloads of my #NuGet package which adds #owasp recommended security headers to #dotnet powered #aspDotNetCore applications.

I'm genuinely humbled.

https://www.nuget.org/packages/OwaspHeaders.Core

I'm also planning on doing a little work on it this week, live on stream.

I'll be taking support away for #dotNetFramework ahead of #dotnet8's release. But don't worry, version 7.5 (current latest) will still work with .NET Framework.

That feeling, when you remove two nuget tooling packages, because the Trivy scanner says they contain high vulnerabilites, and now you have gained a critical in return 🤔
#DotNet #NuGet #CSharp #DevelopersLife

I've published a new #nuget package! AprsSharp.KissTnc will help you interact with a terminal node controller from your C# code.

...in case I'm not the only person in the world trying to interact with #aprs from #dotnet #csharp code. 😂

No guarantees it works for your scenario, but feedback or contributions are welcome! I've tested it with direwolf, so I know that works at least. 😎

https://www.nuget.org/packages/AprsSharp.KissTnc

#hamradio

@kurator88 во, про ямл который не хочется учить это в точку!
Переделал все рабочие билдпланы #bamboo на запуск билдскрипта #nuke, теперь каждый джоб выглядит как 2 таски:
- checkout
- script: ./build.sh JobName

Причем всякий #gitversion, #docker build & push, #nuget push тоже приятно запускать из своих билдскиптов и проекты стали наконец то CI-агностик. Если завтра придется переехать на gitlab, то миграция займет час для 80+ репок.

Обожаю nuke build, их dsl основанный на c# это просто космос. Разрабы могут вкрячить любую логику в билдскрипты без изучения эзотерических #yaml конкретного #ci.

Ну и конечно нельзя забывать про локальную отладку. Все можно отладить на своей тачиле, не будет больше этой пачки коммитов "fix ci pipline once again"

Tomorrow, we have @matkoch - the creator of @nuke - on #2codeOrNot2code to build, test, pack and publish our #dotnet tool as a #NuGet package.

https://www.youtube.com/watch?v=hivyv-iWxck

It's initial release time for our #Roslyn tool! On Wednesday, 19 July 2023, at 17:00 UTC.

Together with special guest @matkoch, we are using the power of @nuke to create CI/CD pipelines that build, test and pack our #dotnet tool to publish on #NuGet, all with #CSharp.

https://www.youtube.com/watch?v=hivyv-iWxck

Wup wup! 🎉🎉 Crossed 10K downloads of Blazor.FileSystemAccess on NuGet this week. It's awesome to see the package being used. 😊
#dotnet #NuGet #blazor
https://www.nuget.org/packages/KristofferStrube.Blazor.FileSystemAccess

Have you ever wanted to create retro looking applications with C# for #dotnet?

Do you want to have Linux or MacOS as a build target as well as Windows? Do you believe that a terminal is a perfectly fine render target?

Well if that's all true, you may just like ConsoleRenderer, available now!

All jest aside, I'm pretty happy with how it's shaping up, and genuinely hope it's useful to someone out there.

Let me know what you think!

#GitHub #NuGet #Foss

https://github.com/NinovanderMark/ConsoleRenderer

Improved .NET Debugging Experience with Source Link → https://blog.ndepend.com/improved-net-debugging-experience-with-source-link/?utm_content=buffer80a0e&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer

Source Link is a Microsoft technology that lets .NET developers debug the source code of NuGet packages referenced by their applications. #dotnet #nuget

Just released a new Visual Studio extension!

NuGetMonitor will show a nice notification if your current solution has nuget packages with updates available.

https://marketplace.visualstudio.com/items?itemName=SamirBoulema.NuGetMonitor

#dotnet #vs #visualstudio #nuget #vsix

First shot at a public #csharp #dotnet open source project. This originally served some business needs for a proprietary platform and has proven useful in other areas. Also includes my first ‘relatively successful’ #sourcegenerators using the IIncrementalGenerator to help generate some boiler plate interface implementations. Also provides a #Serilog sink. All compiled libraries are #nuget feeds #WebLogger

https://github.com/ewilliams0305/WebLogger

#Migration of my #FishingKnots app from #XamarinForms to #dotNET #MAUI is coming along nicely.

The most changes were Namespaces and the common things for switching from #MVVMLight to the #CommunityToolkit #MVVM, plus some minor changes to my already ported private #NuGet packages.

Count is down from above 1500 errors.

#devlife

Small #dotNETMAUI migration progress in my FishingKnots app:

the settings page and its ViewModel have no more errors after pulling in my latest #NuGet packages - YAY! 🙃

#Xamarin #XamarinForms #migration #MAUI #devlife #geeklife

It's just so d*mn #satisfying to watch the #GithubAction to build, pack and deploy my updated #NuGet packages. 😎✌️

#devlife #geeklife #CICD #Github #GithubActions

Well, the National Vulnerability Database is apparently doing away with their legacy feeds, so I'm throwing together a #NVD 2.0 API client for #NuGetDefense that will be published as a #nuget package for #dotnet 6+. This explains the issues I was having getting it to update the NVD feed recently.

I've been thinking about ways to whitelist #nuget packages before allowing them to be installed (explicitly to prevent unauthorized build targets or PowerShell scripts. I'm considering building this sort of protection into #NuGetDefense ( #foss nuget security tool) but I need more insight into how the PowerShell scripts are triggered (ex. Old docs, blog posts, etc). Any insight, ideas, or opinions would be appreciated.