Word Count App does not work with Studio 2019

Error messages at startup

Parents Reply
  • Unknown said:
    Or have I misunderstood your reference to a great wall?

    Hi  

     is referring to the fact we require apps to be upgraded at all and don't provide a framework that means they work in any version.  I think we all wish this would be the case but it's a very simplisitic view based on no knowledge of our internal needs.  In time we'll iron out these problems and continue to improve the delivery of apps as we migrate from one version to another... until then I hope users and developers will be patient with us and enjoy the platform we have made available in the first place.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Children
  • Former Member
    0 Former Member in reply to Paul

    I love the wording you use "simplisitic".
    I clearly remember when MS Word changed their format from .doc to .docx.
    That was a Real upgrade (not this kind of version 2017 to version 2019)
    But, I have not changed anything, not even a line, word or space of my old AddIn (PlugIn) codes of it.
    Even though MS gave me lots, lots of documents to read and adopt,
    they kept their past perfectly, until today I can use the stone aged AddIn (PlugIn).

    That is the real meaning of "simplistic"


    regards

  • Unknown said:

    But, I have not changed anything, not even a line, word or space of my old AddIn (PlugIn) codes of it.
    Even though MS gave me lots, lots of documents to read and adopt,
    they kept their past perfectly, until today I can use the stone aged AddIn (PlugIn).

    I believe that one of the reasons (if not the only one) is that MS Office API uses COM interface, not .Net like Studio.

    This is what I criticized from the first moment I got familiar with Studio API and asked SDL to expose the API via COM again, as it used to be back in Trados 2007 (where automation could be done was SOOOO EASILY).
    It should be basically just a few lines of code... but for some weird reasons SDL keeps quiet and doesn't say anything to it.

    And here we go with the consequences...