Given the awkward way I've recommended integrating archive.exe into visual studio, several users so far have had troubles upgrading to a newer Tailviewer.Api version since their VS post-build event was still using an older archive.exe to pack a plugin targeting a newer Tailviewer.Api version. From now on, archive.exe will print a nice warning to the console in case it detects such a version mismatch. It also points users to checking their post-build event so they have an easier time upgrading their plugins in the future.
Given the awkward way I've recommended integrating archive.exe into visual studio, several users so far have had troubles upgrading to a newer Tailviewer.Api version since their VS post-build event was still using an older archive.exe to pack a plugin targeting a newer Tailviewer.Api version. From now on, archive.exe will print a nice warning to the console in case it detects such a version mismatch. It also points users to checking their post-build event so they have an easier time upgrading their plugins in the future.
Fixes #227