Hi Mariano,
why is that? You can open several instances of PB2017 at the same time on the same machine using the same license.
Why can't we open PB2017 and PB2019 at the same time on the same machine?
Some background on why we would need that to have:
Last year we released a stable version of our product which is based on PB2017 R2 (which is lacking the option to auto log out), which needs to be maintained for about two or three years or even more. As this version is deployed on thousands of machines at hundreds of companies, we are not going to switch this release to PB2017 R3.
In Q3 we will release the next version of our product, which was planned to be based on PB2019.
When we fix bugs in the stable release, of course, we need to also fix them in the upcoming release. So right now, we open two IDEs, copy one snippet from one IDE and paste it into the other IDE. Unfortunately bugs tend to spread across software, so the snippets may come from several events, functions or even several objects.
With the license policy that you offer, this will become a mess as you need to open PB2017, log in, copy snippet 1, log out, open PB2019, paste snippet 1, close PB2019, open PB2017, log in (as I mentioned, we are on R2), copy snippet 2, log out (R2 grrrr), open PB2019 and so on...
I know there are clipboard managers around, but still this will be a mess!
Is there any chance, that Appeon will change this license policy?
I really don't see the point. We bought licenses (plenty of them!!!) which are valid for both releases but we cannot use them at the same time?!? Come on...
For us this is a blocker which will result in NOT upgrading to the new release and eventually neither to those that are still to come.
Please reconsider your policy here...
Best regards,
Marc