Skip to main content
Z
ZS_103838891-Visitor
1-Visitor
December 1, 2022
Solved

Building addon dll from Visual Studio solution

  • December 1, 2022
  • 2 replies
  • 1963 views

Hello my friends,

 

I was required to convert my solution which is based on the makefile in favor of Visual Studio (2019) project. I compiled and built my product using property sheets, but I cannot unlock it with the following message: "Unlocking this application requires option 294." 

I checked all the licensing, and it is perfectly OK. I found the similar case described in 

Article - CS274507 Error "Unlocking this application requires option ObjectToolkitCpp" while unlocking an OTK application even though the OTK license is available as part base license of Creo Parametric. The resolution of PTC is that works as expected and to unlock OTK CPP application user need to have separate
Floating license option of ObjectToolkitCpp (294) license.
 
The unlocking worked fine with makefile. I checked documentation and did not find out what is Floating license or how to use it. Any suggestions?
Best answer by FV_01

it appears you are piling all tasks into msbuild.

to localize the issue, you should try to separate making a dll and unlocking it into two steps - if you could unlock a dll using protk_unlock.bat from a command prompt with working directory set to 'parametric\bin' it would tell you that the most likely problem is your visual studio environment settings.

 

2 replies

V
24-Ruby III
VladimirN24-Ruby III
24-Ruby III
December 1, 2022

Article - "What is the difference between the floating license and locked license": https://www.ptc.com/en/support/article/cs65142

    Z
    ZS_103838891-VisitorAuthor
    1-Visitor
    December 1, 2022

    Thanks. What are the steps needed to obtain this license?

    V
    24-Ruby III
    VladimirN24-Ruby III
    24-Ruby III
    December 1, 2022

    "Get in Touch with a PTC Sales Representative": https://www.ptc.com/en/contact-us

    F
    FV_0117-PeridotAnswer
    17-Peridot
    December 2, 2022

    it appears you are piling all tasks into msbuild.

    to localize the issue, you should try to separate making a dll and unlocking it into two steps - if you could unlock a dll using protk_unlock.bat from a command prompt with working directory set to 'parametric\bin' it would tell you that the most likely problem is your visual studio environment settings.

     

      Terms & ConditionsCookie settingsAccessibility statement