Contents - Index
What's the difference between Sheriff 2 and Sheriff 3?
Sheriff 3 utilises client/server architecture, which differs from Sheriff 2 where a shared file was located on the server. In other words, with Sheriff 3 there are separate Sheriff client/server applications whereas in Sheriff 2 the Sheriff applications only ran on the client. Please read Sheriff Help topic 3.4 for further details.
Is Sheriff 3 compatible with all versions of Windows since Windows 95 or are there some restrictions on either the client or the server o/s?
Do the same evaluation Product IDs and Secret Codes still work
Is the registry path still "HKEY_LOCAL_MACHINE\SOFTWARE\ACUDATA\SHERIFF\PRODUCTID"?
Will my upgrade be as simple as using your new header files and replacing "SlsApi.dll" with "SlsLocal.dll" ?
In other words, I don't have to distribute and deal with your server exe's?
And, of course, my new 3.0 application will recognise existing 2.8.7 licenses on customer machines?
Where is the slsapi.lib file located?
The inc and lib directories have local and remote subdirectories. What is the difference between local application and a remote application?
Is the old method of issuing standalone licenses still supported? That is, can I still access local licenses as files or does all traffic have to be directed through the SlsSevice?
All of our products have a network license option. This would seem to indicate, then, that I would need to know in advance whether I need SlsLocal.dll or SlsRemote.dll. In other words, I'd need a registry key or something similar to tell my app whether to load the local or remote flavor, and go from there. The only other option would be to install the SlsService on all the machines and direct the SLS_Connect command at localhost. Is this correct?
We have several cases where users have a mix of network and standalone licenses. The main application license may be network, but specific libraries may be standalone. Is it even possible to support this case? Can I use both SlsLocal and SlsRemote at the same time? Is the SlsRemote DLL capable of talking to multiple servers?
When am I supposed to call SLS_Connect? The documentation does not say anything about this.
I don't seem to be able to call SLS_Remove when I am not connected. I call this to clear out the registry entries when something goes wrong sometimes, and if something has gone wrong, I will not be connected.
If the server is set to a different port, do I have to set the Clients to that same port when I connect? This will be an additional piece of information needed at setup time.
If the licence files are written to by the server application, do the clients still need to know the path to the licence files? If so, then presumably the SLS_Registry routine will still need a path string? It would be nice if we didn't have to specify this, as it is sometimes a source of confusion for our customers.
So the clients no longer need write access to the licence file?