set(True = false)

Protocol Used between Cicode Editor and Runtime for Debugging

I am working on a VsCode extension for Cicode and have syntax highlighting, antlr cicode parser, code snippets and variable lookup working. But I was wondering if anybody had any information about the protocol used between the Cicode Editor and the Runtime for Debugging? It would be super nice to be able to debug from VsCode.

From what I can see the connection is made over a named pipe 'Citect.Debug' and I can identify roughly how the connection is setup and how the filename and line numbers are requested. But it would be super helpful if AVEVA or anybody had some documentation about the protocol that is being used here.

Parents Reply Children
  • My understanding from that conversation was that the debugging protocol was proprietary and off limits, but that didn't prevent the bits you'd already got working (syntax highlighting etc) from being shared. There are configurations available from users for other editors like Notepad++, but not, to my knowledge, for VSCode.  can correct me if I'm wrong on that. 

    Quite understand that you may have dropped it in a partial state that wasn't suited for release even so, but figured it was worth asking. NP++ isn't a bad editor, it's just that I tend to use VSCode more because it's cross platform.

  • Yes, that was my understanding as well. I just didn't want to give the impression that that was why we weren't releasing it. It was purely a business decision.

    But, can confirm that VsCode does enable some really cool features, especially with the AI codegen integrations, you can almost treat it like a general purpose programming language. Just need a Cicode runtime now so that I don't have to restart Citect every time I need to test things.