Could you please add a Assembly Signature for your library in the next release version？

[longbaochenlong]

Description

My Dear Friend,Could you please add a Assembly Signature for your library in the next release version？Thanks!

Checklist

Please provide the following information:

• Confluent.Kafka 1.0.1.1.
• Apache Kafka 1.0.1.
• Windows10.
• Assembly Signature.

[mhowlett]

yes, we do plan to do this soon.

[zhoubo56]

Our team want change projects into "Strong-naming Assemblies", got the same issue. As the reminder here, we can get the update release immediately.

[mhowlett]

we'll try to get to this this week and put out a 1.1.0.1.

[mhowlett]

this is more effort than I was initially thinking. here's a start: #1000 ... there are issues. I think it's too big a scope for me to get done on the side without getting the ok from product. If you get this working (will also need a PR against our avro fork to make it signed), I can prioritize merging it. It seems like we really only need signed assemblies? (based on what other projects seem to do). seems the downsides to doing that are not material.

[mhowlett]

just doing a bit of research on this ... I now recall that this blog post is responsible for us deciding to distribute a separate signed assembly. however, it seems that advice is no longer good: https://www.pedrolamas.com/2018/09/11/start-strong-naming-your-assemblies/

so, it seems we should move to signing all assemblies and get rid of the separate Confluent.Kafka.StrongName.

[anchitj]

Closing as it's fixed now.