License 2

License 2

Posted by: p.feenstra on 7 October 2025, 9:45 am EST

• 

  p.feenstra

  • Post Options:
  • Link
    Copy

  Posted 7 October 2025, 9:45 am EST - Updated 7 October 2025, 9:50 am EST

  After moving my license to another computer and also upgraded to VS 2022 problems arose with some (older) 32-bits projects.
  
  The projects were copied and pasted to the new computer. The applications are compiling and run without errors.
  
  But when I try to open a form in the designer (VS 2022 issue), it doesn’t load due to licensing issues. (image)

  Regards Piet

• 

  aastha.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 8 October 2025, 12:20 am EST

  Hi Piet,

  Thanks for the sharing the snapshot.

  As per our understanding, the issue is occurring because of the incorrect/missing runtime license file(.gclicx) in your project. To license an application that uses Spread.NET, a runtime license (.gclicx file) must be added to the project as an embedded resource. This .gclicx file can be generated with different names based on your project scenario. The two scenarios are discussed below:

  (1) Using Spread Controls Directly in Your Executable Project:

  In this case, you need to generate a .gclicx file named “ApplicationName” and embed it in your application.

  https://developer.mescius.com/spreadnet/docs/versions/v15/online-win/spwin-createruntimelicense.html

  (2) Creating a Class Library/User Control with Spread.NET Control and Referencing These DLLs in Your Main Executable Project:

  In this case, you need to generate a .gclicx file named “ApplicationName.ClassLibraryName” and embed it in the class library project.

  https://developer.mescius.com/componentone/docs/license/online-license/license-user-controls.html - This is C1 Licensing documentation, but it works same for Spread.NET. You just need to use the Spread.NET product ID “f36c83c3-49ab-46b8-bfe2-8b19875ea597”.

  If you still face any issues, please share the following information:

  (1) The .gclicx files that you generated by following the scenarios above

  (2) Some details about the structure of your project. Are you creating a Class Library/User Control using Spread control? If yes, please provide more information about the reference structure, such as which project references which, and which ones use Spread control?

  3. If possible, please share a stripped-down version of your sample application that replicated the issue.

  Hope this helps you!

  Thanks & regards,
  
  Aastha

• 

  p.feenstra

  • Post Options:
  • Link
    Copy

  Posted 8 October 2025, 1:09 pm EST

  Hi Aastha,

  Thank you for your quick response.

  I created a .gclicx file and placed it in the project as you indicated. (named as “.gclicx”)
  
  But since that didn’t work I decided to go back to VS 2019 for my older 32 bit projects.
  
  VS 2022 doesn’t handle 32-bit Windows forms well. It causes too many problems, and I don’t have the time or money for it right now.
  
  https://learn.microsoft.com/en-us/dotnet/desktop/winforms/visualstudio/troubleshoot-32bit

  Regards Piet

• 

  aastha.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 9 October 2025, 5:54 am EST

  Hi Piet,

  Thanks for the update. We understand your decision to continue with VS 2019 for your 32-bit projects. If you revisit VS 2022 later, we’ll be glad to assist with any licensing or setup issues.

  For license related issues, we suggest you post the request on our private portal: https://developer.mescius.com/my-account/my-support

  Best regards,
  
  Aastha