Difference Between LabWindows/CVI Full Development and Debug Deployment Licenses

Issue Details

I am trying to activate a LabWindows/CVI license for a production line. When activating the license, I did not find a "Debug Deployment License" option listed. Instead, I see the following options in NI License Manager:

• Full Development System
• Full Development System(Debug Only)

I tested the CVI Full Development System(Debug Only) license, and I can modify the code, set breakpoints, and build DLLs with it.

I would like to know:

1. Is Full Development System(Debug Only) the same as the Debug Deployment License?
2. What are the limitations of the Debug Deployment License? Can we modify code, set breakpoints, and build DLLs with it?
3. What is the difference between the Full Development License and the Full Development System(Debug Only) license?

Solution

The LabWindows/CVI Debug Deployment License and the LabWindows/CVI Development License are functionally equivalent but differ fundamentally in their legal terms of use under the NI General Purpose Software License Agreement .

Below are the answers to the specific inquiries regarding these licenses:

1. Is Full Development System (Debug Only) the same as the Debug Deployment License?

Yes. In the NI License Manager and activation portal, the license that activates the LabWindows/CVI Debug Deployment License (Part Number: 781148-35) is represented as Full Development System(Debug Only) .

2. What are the limitations of the Debug Deployment License? Can users modify code, set breakpoints, and build DLLs?

Technically, there are no software feature blocks or design-time limitations. You have full access to all design-time and debugging tools within the LabWindows/CVI environment . This means you can:

• Modify code.
• Set breakpoints and debug.
• Rebuild and build DLLs, executables, or libraries.

However, there is a legal limitation under the NI Software License Agreement:

• Usage limitation: A debug license must only be used on a target/deployment machine to periodically resolve, debug, and fix issues on an application or system that has already been created with a development license . It must not be used as a primary development seat on your main development workstation .
• No Home Exception: Unlike development licenses, debug licenses do not include a home exception .

3. What is the difference between the Full Development License and the Full Development System (Debug Only) License?

The key differences lie in their intended use-case policies and seat assignments:

• LabWindows/CVI Development License:

  • Purpose: Used for creating and developing new applications and programs from scratch .
  • Installation Policy: A Named-User (Non-Concurrent) development license allows a single user to install and activate the software on up to three computers (e.g., primary workstation, field laptop, home computer) with the condition that only one instance runs at a time .
  • Home Exception: Includes a home exception .

• LabWindows/CVI Debug Deployment / Full Development System (Debug Only) License:

  • Purpose: Used to fix issues on an application or system already deployed to a production or test system .
  • Installation Policy: Restricts installation to a single target computer .
  • Home Exception: Does not include a home exception .