I've found a side effect of C# now also using ! for null- uppression is that I find myself more inclined to use "== false" or "== true" for bool checks.

So:
boolVariable == false
instead of
!boolVariable

Not sure if I like the null-supression ! because of this.

#dotnet

I have an older legacy project where integration tests isn't set up and would be quite complex to do, so using "unit tests" mechanics via substitutes and executed call checks - it works, but a bit cumbersome to write and maintain, but still loads better than manually testing complex import flows.

#unittest #dotnet #legacycode

Thinking of moving away from 1Password as manager.

Anybody have a trustworthy and relative user-friendly European based, non AI entangled, one to recommend?

#passwordmanager #recommendation #danmarkskifter

Memo-to-self; When cleaning your inbox, that means the old error mail that's now on top - is not from today.

What are the strategies for recovering from failed startup (500.30), more or less automatically in dotnet 9/10 running in IIS;
e.g. external resources or database are (temporarily) unavailable in the startup for migrations.

It seems the startup is not run again, if it failed.

(It's legacy code as well, so cannot rewrite being dependent on external in startup right now)

Is it a (powershell) script based direction - heartbeat/recycle pool; A try-catch in startup with retry/sleep?
Other?

#dotnet #iis

RE: https://agilealliance.social/@mlevison/116014353496094349

One thing I also consistently see, is the argument that the "AI" can solve/code our problems much faster, because 'we' either lack the knowlegde ourselves, or it would take too long to obtain it .....
Yet, the expectation is then that those who lack the knowlegde still somehow must verify the product and the result......
I'm floored by the lack of reflection every time I hear that argument

Sure it might be easy in some POC or low hanging problem-fruit, but how long until the push towards "more", "faster", "less supervised".

After fighting with DevOps over testing some legacy time conversions; I managed to fail a unit test because I used a control date from before daylight saving was introduced, so my expected offset was incorrect :)

I feel old.

#dotnet #unittest #test

Ahh thank you again "dotnet nuget why" - you saved me much work.

#dotnet

Had a colleague that had a problem, and "even ChatGPT had to give up".... he showed the error message, 30 seconds searching not looking at (wrong) AI answers, found the github issue and solution.

It's not that I hate AI (well......) - but I hate what it does to people.

#GenAI

Is it possible to control the installation directory and especially drive of #dottrace
Can't seem to find any setting in the installer menu?

#jetbrains #dotnet

So made a source generator - ended up rather complex.
But I find unit testing it very tedious when verifying the generated output via Verify.

Is it not possible to load a class/instance as source in the testing, and use it as foundation for the generator. Instead of having to manually writing (and maintaining) the source as a string to then parse into a syntax tree to verify output? I mean it can generate on compile time, so why not at test? :D

#dotnet #sourcegenerator #unittest

Asking #copilot if I can do X with including Y in dotnet. And get a reply of
'yes, here's the <code I, myself, just wrote to test>".
But I get an error if I do this.
'Yes, you just need to include Y'

/facedesk

I find documentation, and quality blogs increasingly difficult to come by for solving dotnet issues. And then you run into the meme of finding a post with the same issues from years ago (in old versions) without any significant answers..... TGIF

#programming #dotnet

I'm disliking "SPA" more and more. It seems like so much work and code and complexity for no real additional UX/UI benefit. Maybe it can do some "cool" swoosh animations or something, but really.....
#developers

It can be annoying to see all the null reference warnings and nullable handling in newer dotnet versions, until you open an old project, again, to fix yet another null reference exception.

#dotnet

It's funny, I've always struggled with 'imposter syndrome' and wanting to always be/do better, know/learn more, and actually do something constructive.

But the more I learn, the more experience I get, it's still getting harder for me to balance the feeling of inadequacy and ambitions

Which tool(s) does #dotnet people use to performance/stress test API's?
I use(d) BlazeMeter/JMeter in the older days, but I was wondering if there were other/better things?

#test #performance #dotnet #api

I find it weird that writing on Teams (or similar messenger) asking if they can disturb is still a thing.
It's not like messenger systems is something new in the office anymore and of course it's interrupting to ask if you can interrupt.

Oh and also people writing "Hi" as a single message, and then 30 seconds later still is typing follow up.

#PetPeeve #RantOfTheDay

Happy 41st birthday :-)

Being good at debugging, might be because I've made many mistakes over the last 20 years. 😅 #development #programming