Should I strongly name all assemblies?

Question

So there are lots of questions around the benefits of strongly naming a .Net assembly, such as this one Why use strong named assemblies?

The benefits sound great, so why wouldn't I strongly name every project I make?

What are the advantages of NOT strongly naming an assembly, and which should I do by default when making new projects?

Answer 1

Strongly naming an assembly takes time (sort of) and is not useful for a project that you don't plan to take to the market/open-source it. There are some implications when you do not strongly name your assembly, such as you cannot add it to the GAC.

A possible benefit is that you can reference other unsigned assemblies within your assembly, whereas in a strongly named assembly you can only reference other strongly named assemblies.