Skip to main content
J
JA_136925671-Visitor
1-Visitor
June 22, 2025
Question

Subject: Request for COM Automation SDK or Implementation Behind CLSID

  • June 22, 2025
  • 2 replies
  • 795 views
Hello,
I’m using Mathcad Prime 11 and have registered the Automation DLL successfully. However, when attempting to instantiate ApplicationCreator, I receive E_NOTIMPL. I confirmed that CLSID {A00EB895-D415-433F-A04E-D298A45A7BB7} is registered and points to MathcadPrime.exe, but it appears that the actual COM implementation is missing.
Could you confirm whether Mathcad Prime 11 includes the full Automation COM server implementation, or if a separate SDK or license is required to enable ApplicationCreator and related interfaces?
Thanks,
Johnny Abudayeh

2 replies

T
21-Topaz II
terryhendicott21-Topaz II
21-Topaz II
June 23, 2025

Hi Johnny,

SDK is called an API in Prime

The API is included with a Mathcad Prime full license.

There are some good examples provided in help of how to create Custom Functions or Applications that use Prime for many languages.

It is suggested to look at them.

What programming language have you chosen from the ones available in the API.

Capture.JPG

Cheers

Terry

 

 

    T
    21-Topaz II
    terryhendicott21-Topaz II
    21-Topaz II
    June 23, 2025

    Hi Johnny,

    Capture.JPG

    Just to be clear.  Custom Functions can only be written in C, C++, or Fortran in a C wrapper.

    Cheers

    Terry

     

      V
      vnamboodheriCommunity Manager
      Community Manager
      June 27, 2025

      Hello @JA_13692567, 

       

      It looks like you have a response from a community champion. If it helped you solve your question please mark the reply as the Accepted Solution. 

      Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

      Thanks,
      Vivek N.
      Community Moderation Team.

      T
      tKkagF0R9b19yoW7-Bedrock
      7-Bedrock
      June 27, 2025

      I have also recently upgraded to Mathcad Prime 11.0.0.0 (version 9 was removed first), and none of my existing COM automation can connect to the Mathcad Prime COM API (Error as follows: -2147221005, 'Invalid class string').

      Even browsing to the TLB using the MS Excel VBA developer window allows the class properties to be viewed and added as a reference to the project, but running the project results in -2147221164 'Class not registered'.

      J
      JA_136925671-VisitorAuthor
      1-Visitor
      June 27, 2025
      Hi there,

      I have encountered a problem that Mathcad Prime 11 current Net Framework version is 4.0 for (Ptc.MathcadPrime.Automation.dll). I have had so much trouble looking for this specific version. Why PTC is not up to date with the new .Net versions? Microsoft is at version 9.

      These errors were consistent in Visual Studio 2022:

      CS1061: 'IMathcadPrimeWorksheets' does not contain a definition for 'Add'

      CS1061: 'Worksheet' does not contain a definition for 'SetExpression'

      CS1061: 'Worksheet' does not contain a definition for 'Evaluate'

      CS1061: 'Worksheet' does not contain a definition for 'AddTextRegion'

      CS1501: No overload for method 'Save' takes 2 arguments

      CS0117: 'SaveOption' does not contain a definition for 'DoNotSaveChanges'

      Ptc.MathcadPrime.Automation.dll Runtime Version: The error message "The primary reference "Ptc.MathcadPrime.Automation" could not be resolved because it was built against the ".NETFramework,Version=v4.0" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.6.2"." is a critical clue. It indicates the Mathcad DLL was built for .NET Framework 4.0.

      This version of .Net Framework 4.0 seems also no longer supported by Microsoft. This is a huge issue.

      Please help.

      Thank you,

      Johnny Abudayeh P.E., ASCE M.
      Principal

      Structural Optimal Solutions, LLC
      Rockville, MD 20850
      Cell: 202-669-5018




      Terms & ConditionsCookie settingsAccessibility statement