Basically, you assign one Program ID to protect an application. When you issue an upgrade or bug fix, you still use the same Program ID. This makes the upgrade transparent without requiring a new license. If you wish to release a new major version, you assign the new version with a different Program ID. So users who wish to upgrade must register for a new license.
In addition, using Program ID together with Module ID allows you to protect your applications in many different ways. The example below shows how to apply Program ID / Module ID to a product with different editions.
|
Windows 10 |
Program ID: 0 |
– Home Edition |
– Module ID: 1 |
– Professional Edition |
– Module ID: 2 |
|
From the above, users who own Windows 10 Home cannot use the features available in Windows 10 Professional. However, they can upgrade edition later through Module ID 2.
The example below shows how to apply Program ID / Module ID to multiple lines of products.
|
Office 2019 |
Program ID: 0 |
– Word |
– Module ID: 1 |
– Excel |
– Module ID: 2 |
– PowerPoint |
– Module ID: 3 |
|
|
Visual Studio 2019 |
Program ID: 0 |
– C# |
– Module ID: 1 |
– VB.NET |
– Module ID: 2 |
– VC++.NET |
– Module ID: 3 |
|
From the above, you can license your products based on customer needs. For example, users who want Office with Word only can be licensed through Module ID 1. They can upgrade license to include Excel, PowerPoint through Module ID 2 and 3, respectively.