Same build number for both?  Should we expect that from now on?

If we have BOTH VEPRO and VIPRO - we just update VEPRO, right?

If you use both, update both. They are seperate applications.

Thanks Karel.  All the best,

I've never needed any VE Pro license on the eLicenser plugged in my Host machine, as I'm running both VE Pro Server and any other VI / VI Pro plugin instance in the remote servers. In fact, I could run both the VE Pro setup and the VE Pro plugin inside my host software without any VE Pro license in my eLicenser key.

Now, I've just noticed that you need a VE Pro license in the eLicenser also during the setup. I think this is just an error in the setup executable, as it never happened before. In fact, I installed any previous version of the VE Pro on my Host without any VE Pro license.

I can also confirm that, once the new VE Pro 6853 is installed, you can remove the eLicenser and the plugin inside your host loads without any issues, as it did before.

This makes my think that something went wrong compiling the setup executable of the last VE Pro release 6853.

You're right. Running the VE Pro Server Interface plugin requires no eLicenser at all. The license check is there because the installer installs both the VE Pro Server and the VE Pro Server Interface plugin.

I get your point, but the fact is that check has never been there before. I always installed every previous release without having any license on my eLicenser. Your consideration about the double server/plugin installation doesn't justify, in my opinion, this change. In every previous version you could install both of them, but you couldn't run the server without the license. This approach makes absolutely more sense to me. And in fact, this approach was the one for any previous version.

It's not a big deal to move one key to the Host just during the setup. My wonder was about the reasons why you decided to change this behavior.

Yes, checking the license in installation is really shortsighted especially from a company that helps us use slave computers. We have computers without internet connections, without keyboards, without displays etc. and the computer used to extract or install the downloaded software isn't necessarily the computer used to run the software. No other company I know of does that and I'm disappointed that VSL would do something like this. If you trust the dongle then trust it. If you don't then don't make us use it.

I wouldn't say I'm disappointed of this change. I was just curious to know if it's a precise choice or just a mistake compiling the setup executable for the latest release.

@Gemini said:

I wouldn't say I'm disappointed of this change. I was just curious to know if it's a precise choice or just a mistake compiling the setup executable for the latest release.

How do you find the new licence scanning time? Is that better?

DG

@DG said:

How do you find the new licence scanning time? Is that better?

Way much better. It's almost immediate and this is particularly noticeable when you open the VE Pro Server after a fresh start up of the system. In the same situation with any previous release, it took a way longer time, especially to scan the licenses.

I'll just remove that license check for the next update. It doesn't make much sense indeed.

Thank you Karel!

I really appreciate your kind consideration! [;)]