Just noticed a nice quality of life improvement for #dotnet devs using #JetBrainsRider. When in the #NuGet Tool Window, you'll also see if a project has a dependency implicitly installed in the project.
Unit testing support in #JetBrainsRider for a #godotengine game is slick. Rather than fiddling with magic numbers, you can write tests using #GDUnit4 and get a better feedback loop.
You only need the #NuGet package, too, so you don't have to add the add-on to the game.
Why is it that almost 100% of the time when I go to create or use a #dotnet#dotnetmaui project in #visualstudio that it just fails to build for random reasons - like being unable to find the right #nuget packages or some other obscure b.s. that requires lengthy searching and trial-and-error to maybe fix?
Basically, my experience with #dotnetmaui almost always sucks.
Well, I can certainly build #PowerShell for #FreeBSD now. I might be able to just "fake" a #git working copy for its stupid build system. This still doesn't fully solve the version issue, it insists on appending the git hash -> TODO.
The "login shell" feature can be added, an exercise left for later, the code will look pretty similar to the existing MacOS-X implementation. Maybe upstream would even accept it 😎
For a #port, it should probably be "published" as "#ReadyToRun" (I hope this has no negative impact), otherwise lang/dotnet would become a hard run dependency ... This works now as well, but requires changes in lang/dotnet ... requires some platform-specific #NuGet packages that don't exist on MS servers for FreeBSD. They are created during build of dotnet itself, but not installed anywhere by default ... I'll suggest an "on by default" port option to bundle these with lang/dotnet.
@nblumhardt So in general for redaction, the suggested approach is I write my own custom redacting sink?
Would it be worth to put all the redaction functionality into a reusable #serilog#nuget package?
We have a #dotnet based framework (a bunch of #nuget packages) that can be used to build desktop executables that control and visualize machine data with a very simple and easy to use #MVVM based API. It is based on #WPF and we want to rewrite/redesign it to make it cross platform.
What UI technology should we base it on?
Customers will have to learn the basics of that chosen technology.
NuGetSolver is a powerful Visual Studio extension designed to help you tackle NuGet dependency conflicts with ease. It takes into consideration all dependencies and provides intelligent and automated suggestions to resolve dependency conflicts in your projects.
I'm shipping binaries compiled against netstandard1.1 and the NuGet reference I bring along is NETStandard.Library version 1.6.1.
Does anybody know any reason I can't just bump that up to version 2.0.3? It seems like it's just a more complete collection of dependencies for runtime.