hi @anuj-modi , thank you for using NRedisStack and letting us hear about your case.

I noticed there have been other requests related to signing, but it seems it didn't make to the master branch anyway. I'll need to look into those requests further to understand all the details. It also appears there might be some confusion around package signing vs strong-naming the binary.

Having said that, it's clear that your request specifically concerns strong-naming the binary. There are a couple things to evaluate there too, especially with open-source projects as i read. 👉 https://github.com/dotnet/runtime/blob/main/docs/project/strong-name-signing.md

I ll dig in more and keep it updated here. For the time being we are busy with other tasks so i can not provide a clear timeline for it.

Hi @atakavci. Definitely appreciate you taking a look at this. I made a PR that adds the strong name signing. I understand there are more considerations on top of simply doing the signing, but hopefully this makes your job a little easier.