Versioning our DLLs

[Cantor, Scott]

On 7/7/17, 5:34 AM, "dev on behalf of Rod Widdowson" <dev-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:

> I happened upon an oddity yesterday in that messages.dll doesn't carry a version.  This dll is where the various translations (well
> US English) for our messages go - the ones that end up in the event log.  So long as we are careful about numbering (always add
> to the end of a series) the only side effect of being out of date is that the event log cannot print anything - but the event carry
> text anyway so you know what's going on.  Plus of course absent a version the date is used.  So all in all I don't really care and I
> don't think that we should.  Should we?

When did that get added? I think I asked you to create that, right? Doesn't seem like we had until 2.6 maybe?

> Do we think that there is any value in using a common header file and including it in the resource files?  It would save time and
> risk during the release process.

Clearly, I'm just lazy.

> Of course there are situations in which we might want to modify the version values per dll, but I don't think that they are
> common or insuperable.

I've been inconsistent on that. It isn't always clear to me if they should change or not, but with the installer we have now, the simple thing is just to always bump everything in patches and not try and play games with what actually changed. You never really know what gets rebuilt, and even though I try and limit inlining, with C++ that's just always in question with templates and other things. It's best to be safe.

-- Scott