Versioning DLL's

The component Neuron uses for it's Pipeline code step stores the fully qualified assembly name. This causes issues sometimes for people who have set up assembly versioning in their projects.

When we ask people why they are versioning an internal dll that they never intend to run side by side the most common answer we get is so they can be sure the right one is deployed to production.

So, how can you achieve a process where you provide yourselves this kind of information and not break your pipelines and everything else that uses a fully qualified assembly names? Use File Versioning (AssemblyFileVersion attribute) instead of assembly versioning.

This will allow references to your strongly named dll to continue to work and will give you versioning information.