Comments by Veener (Top 3 by date)

This might work, but I'd prefer a solution that can be executed using the command line so the build machine can run it easily.

I don't prefer this solution because the assembly itself still has only 1 default icon that would be shown in Windows Explorer. It is nice to be able to choose the icon when creating the shortcut though. By going this route, I would lose auto versioning (AssemblyInfo.cs) and app.manifest. Not really what I'm looking for.