How are custom assembly versions determined for the admin UI?

The custom assemblies panel currently displays the .net assembly version, which is often fixed and doesn't change between builds.

Karl Barber said:

Is it possible to alter the information shown ? 

re: your question

Yes, for your own custom plugins, you can set the assembly version per build in the csproj file (e.g. <AssemblyVersion>14.0.12.0</AssemblyVersion>), and after you rebuild and redeploy, the panel will show the exact build. Please test this first, as changing the assembly version can break binding if other assemblies reference that plugin. For 3rd party libraries, the assembly version is fixed by the vendor, so it can't be changed on your side.

The custom assemblies panel currently displays the .net assembly version, which is often fixed and doesn't change between builds.

Karl Barber said:

Is it possible to alter the information shown ? 

re: your question

Yes, for your own custom plugins, you can set the assembly version per build in the csproj file (e.g. <AssemblyVersion>14.0.12.0</AssemblyVersion>), and after you rebuild and redeploy, the panel will show the exact build. Please test this first, as changing the assembly version can break binding if other assemblies reference that plugin. For 3rd party libraries, the assembly version is fixed by the vendor, so it can't be changed on your side.

Karl Barber is out today, but this doesn't answer the question. You can clearly see from Karl's original screenshot, that the assembly version is set and shows in File Explorer as 33.1.0.26 but in Community it is shown as 33.0.0.0. We know how to set the assembly version, but Community is only showing the major version, so we cannot see which assembly versions are deployed.