Is there a .NET equivalent for the License Collection?
Visual Basic 6.0 allows you to dynamically load ActiveX controls when an application is running. Some ActiveX controls require the use of a license for them to be used within a program. The Licenses collection of an application contains the license information for all loaded ActiveX controls and allows you to add and remove each license as needed. The licensing model in Visual Basic .NET is completely different, so upgrading applications that use the Licenses collection requires some effort. Visual Basic .NET compiles the license directly into the executable. That means that the control must already be present in the project before it can be dynamically added at run time. Thus, license management cannot be automatically upgraded, and an alternative strategy must be applied in Visual Basic .NET. One way to do this is to add a dummy form to the project and put all ActiveX controls that will be dynamically added to this form. After you create this dummy form, you can dynamically add the A
Related Questions
- If the current end-user number exceeds the end-user number allowed by my Site Collection License/Farm License, what will happen?
- What is the difference between a Server License and a Site Collection License/Farm License?
- What are "end-users" and how do they affect my Site Collection License/Farm License?
