Firstly; thanks for all the answers.

@ sundialsvc4

Re: The client's justifiable concerns for security could in fact be addressed by implementing, within that "privileged account," an entirely self-contained and isolated Perl installation ...

Maybe a naive question, but why should address this the clients security concerns? Could You please elaborate this remark a bit?

Anyway, I think my client and me are beyond this discussion already. He just would not understand and allow such a scenario.

From my point of view my client and me should come to a solution which is as independent as possible from the Windows version, just to keep the maintenance effort low.ญญญญญญ But since we cannot exclude in advance differences in the dependencies from (windows) version to version, I am afraid we cannot avoid holding three (virtual) machines available for development with the corresponding windows versions installed.

Unfortunately, there is only scarce information on the compatibility of the Perl interpreter with the windows versions, but from my research it seems that there will be no single Perl version which will work with all windows versions, which makes things more complicated.

Since the situation is like this, my approach would be to develop and compile script(s) into executables on those three different machines, but NOT including the Perl interpreter (the tool will be transferred to the production system prior to each deployment, so the file should be small).

Does this make sense?

And: is it worth to TRY to run the executable generated on the newest Windows version (2019) on the other two versions? (hoping their will be backwards compatibility)

In reply to Re^3: Running compiled Perl script on different Windows Server versions by Bloehdian
in thread Running compiled Perl script on different Windows Server versions by Bloehdian

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.