Licensing, Feature set & continuous integration

Discussion created by philbeeson on May 17, 2013
Latest reply on May 19, 2013 by matthewb
Generally, I think I understand the theory behind ESRI's licensing for SDK for WPF.  However I still have some practical questions relating to our required use case.   I'd appreciate anyone with insight to share their experience or knowledge, I can't be the first person to tread this path.

Our GIS requirements are generally very simple, most of our customers will manage with just a tiled base layer with a few icons on a graphics layer dynamically generated locally.   As far as I can see, these customers will be adequately served by a basic license.   Some of our customers will also want to add layers generated from local shape files, for which we will need standard licenses.   Is there any way we can dual license the SDK and have the feature set entirely dependent on which licence the customer has been supplied with?

Our GIS functionality is just a small part of a much larger PRISM based application.  The GIS functionality needs to be implemented as a dynamically loaded module within our application.   Not all deployments will include that module or the ESRI assemblies.  All the documentation I've seen referrs to embedding the license string in the application.   Would the licensing technology still work if the licensing string is embedded in the assembly that implements all our GIS module?  This assembly would be the only one in the application that references any of the ESRI assemblies.

We use a separate build machine to the developers machines and run on demand and scheduled builds on this machine,  can this machine build applications without a developer license? (There is no developer for this machine, it's just used as a controlled environment for CM builds).