LongSack posted:

TooMuchAbstraction posted:

I'm getting an error at the Add statement in Subscribe: "cannot convert from System.Action<T> to System.Action<PubsubEvent>". Which is strange, because the function has a constraint on it that T must be a PubsubEvent. Any idea what's going on here?

TooMuchAbstraction posted:

Thanks! Jabor gave a similar response in the General Programming thread. It's unfortunate, but the type-unsafety is kept to a small part of the code so I guess I can live with it.

If you'd care to, I'm curious what your opinions are about the design.

Polio Vax Scene posted:

I'm lost and need some guidance. We're building an integration with a third party that uses JWTs to authenticate users. The tokens are signed using an x509 cert.
When I use the System.IdentityModel.Tokens.Jwt package to generate a token, it adds an x5t header to the token. We need this to be an x5c header instead, as the third party will not support x5t signed tokens. I've been struggling to find a way to change how the token is signed with no luck.

rarbatrol posted:

You could wrap the sync method in something like await Task.Run(stuff) or put an await Task.Yield just before it and it may behave a little better for you.

adaz posted:

an oldy but a goody on async await TPL best practices from Tech Ed 2014

Async Await best practices from MSDN Magazine.

TPL pitfalls from MSDN

Rocko Bonaparte posted:

I had seen your response yesterday but I had to double check something today. I also have a similar with where I use a List<> and I thought Equals() was comparing contents there. But I checked it today and bam, I am manually comparing contents. So that is what I get for 2AM coding.

nielsm posted:

Case folding is a particular algorithm/transformation specified by the Unicode standard, yes, and it isn't quite the same as an "uppercase" or "lowercase" function, which is by definition human language sensitive.

Searching I find this: https://github.com/dotnet/corefxlab/pull/2637
But I can't figure out where this is supposed to be implemented or available. The PR says it's merged nearly 3 years ago, but I don't see any trace of it in the .NET 5 or 6 library. Maybe System.Text.CaseFolding is available as a NuGet package?

fuf posted:

man I still have such issues with EF and saving related entities. I just don't get it at all.

[...]

So then I think ok, maybe I need to attach the Filters in the db to the current context so that it doesn't try to insert duplicates? Like this:

C# code:

using var db = contextFactory.CreateDbContext();
var Filters = db.Filters.ToList();
db.Playlists.Add(playlist);
db.SaveChanges();

But then the error is:
"The instance of entity type 'Filter' cannot be tracked because another instance with the same key value for {'Id'} is already being tracked."

I think this is because the context now has two versions of the same Filter object: one from the DB and one attached to the Playlist object.

How can I tell the context that they're the same object??

insta posted:

I know the compiler converts simple, compile-time string concats into a string.Concat call -- but I'm seriously surprised it can't figure out how to do that for the Interpolated example in my code.

epswing posted:

Am I missing something obvious here?

epswing posted:

I'm having more fun with AspNetCore logging.

epswing posted:

Ah you're right, the settings.json file is controlled by the Azure "App Service logs" UI page


Here's the before/after changing from Warning to Information in the UI


Of course, when it's set to Information I see Microsoft's noise, and when set to Warning, I don't see my Information logs.

I wish this was more obvious. There's all this documentation about how to configure and fine-tune logging via filters, and none of it matters at all if you're using Microsoft.Extensions.Logging.AzureAppServices? So basically anyone doing anything of substance is using NLog/log4net/serilog/etc? Unless I'm misunderstanding something, what sense does it make for the Azure logging provider to not reference and filter the categories set in the project's appsettings.json file.

Edit: Found it here

NihilCredo posted:

C# code:

var thing = fetchSome(usershit);

if (thing is { SomeProperty = null }) {
   log("your poo poo is hosed");
   return;
}

DoSomething(thing.SomeProperty);

The guard clause desugars to "thing?.SomeProperty == null", so it will catch a null 'thing', which is the right choice. But having a specific property being null is a different error than the entire object being null (the former means the client hosed up, the latter could be the fetchSome function that hosed up).

Red Mike posted:

Property patterns won't throw if it's null, it'll just early quit and act as if it's not a match.

From https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/proposals/csharp-8.0/patterns#property-pattern.

Munkeymon posted:

I'm trying to hook up Azure App Services running a Framework ASP monolith up to an App Configuration service and I've almost got it working with just web.config changes, but I can't figure out how to load the connectionString (or endpoint for that matter) from the environment/App Service's Configuration. Is there some "magic" way to tell the config parser to grab a string from the environment's connection strings or... something? Configuration builders section of the config for reference:

code:

  <configBuilders>
    <builders>
      <add name="AzureConfigurationSerivice" connectionString="halp what do here?" mode="Greedy" type="Microsoft.Configuration.ConfigurationBuilders.AzureAppConfigurationBuilder, Microsoft.Configuration.ConfigurationBuilders.AzureAppConfiguration, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      <add name="Environment" mode="Greedy" type="Microsoft.Configuration.ConfigurationBuilders.EnvironmentConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Environment, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
    </builders>
  </configBuilders>

That works as long as I crack open the live config and paste in a connection string, but obviously that's not gonna cut it for automated deploys and eventually I'd want to either put the string in a keyVault or, better, just pass it the endpoint and let IAM do its thing. Anyone here made this work?