Getting Rust's tokio and .NET’s async runtime talking to each other via the C ABI

How do you deal with ever expanding migrations and the need to squash them?

Each migration comes with a huge designer file, which ends up being a bottleneck when migration count stacks up: whenever doing a new migration, it takes more time than before / uses more resources because the migrator is scanning all designer files as well as all the migrations.

The solution is “squash the migrations and you’ll be good”. And that works.
But squashing the migrations is a coordinated process, because it means (at least for us) squashing and then updating the migration project on any open branch. Add to this the custom SQL when there is some.

Basically squashing is a bottleneck for us, and I’m wondering if there’s a default process to deal with this in EF. Or how people in other company deal with it

I’ve been on ASP.NET Core MVC for a while now, and it’s been solid. But lately, seeing where Microsoft is pushing Blazor, I’m seriously considering it for our front-end websites — not just the back-end admin panels. At work, I’m even planning to recommend it.

The catch is our sites run behind load balancers. Sticky sessions we can set up, no problem. But I’m not sure how SignalR behaves with them. Cookie-based sessions transfer fine — we can re-authenticate users on a new server without much drama. But the SignalR connection and the UI state?
That’s the part I don’t have a clear picture of.

If by a server breaks or gets overloaded and a new instance spins up, what does the user actually see? Does the UI just forget everything — form fields, button states, the works? I suspect it behaves more like a page refresh: the user loses their current state, but sessions and cookies get managed anyway. Still, I’d like to hear from people who’ve actually run this in production.

Hello Everyone, I am Recently Searching for a good Open-Source Complete Free AWS-Emulator for local-development, i find some emulators in internet.

1. LocalStack : it is only for hobby and not for commercial usage and only have 30 free services.
2. LocalEmu : It is completely free and Open-Source and have 132 AWS services.
3. Floci : It is completely free and Open-Source and have 75 AWS services.

What is Surprising to me LocalEmu and Floci both are completely free and Open-Source but Floci have only 75 AWS services but it has 23k github stars but LocalEmu has 132 AWS services but it has only 179 stars in github.

Why LocalEmu is not popular still have lot of services then Floci and it is still completely free?

I search about LocalEmu in youtube i can't even able to find a single video about LocalEmu, when i search about LocalEmu in youtube only LocalStack is coming in front, why youtubes not speaking about this amazing AWS-Emulator?, Is have any issue with this emulator?, because github star is too low so i getting this question?

localemu floci

Hi everyone!

I’d like to share with the community a project I’ve been working on in C#.

It’s a project that uses Hangfire for task processing and RavenDB as the database. The package responsible for this integration is outdated and is no longer maintained, so I decided to continue working on it and keep this ecosystem maintained and up to date.

It’s something I started mostly out of curiosity because I thought it would be interesting to work on this integration, and I wanted to share it with you all.

https://github.com/kelvinaxhcar/Job-Hangfire-RavenDB

https://www.nuget.org/packages/Job.Hangfire.Raven6x/1.0.7#readme-body-tab

Hi

I wrote some unsafe C# code which is working just fine even though it was hard to figure out :) but i would like the code to be cleaner.

here's my code:

public static unsafe delegate* unmanaged[Cdecl]<byte*, byte*, byte*, int> callback = null;

[UnmanagedCallersOnly(EntryPoint = "RVExtensionRegisterCallback", CallConvs = new[] { typeof(CallConvCdecl) })]

public static unsafe void RVExtensionRegisterCallback(delegate* unmanaged[Cdecl]<byte*, byte*, byte*, int> cb)

{

callback = cb;

}

And this is how i would like to have:

public unsafe delegate* int DelType(byte* a, byte* b, byte* c);

DelType callback = null;

But that does not compile due to the delegate*

I guess its not possible to use DelType with unsafe code or am i missing something?

Any feedback on how to improve is welcome :)

thx!