This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Debugging UI Extension App in VS 2019

Hi community and M-Files,

We are following instructions provided in www.m-files.com/.../ technical article to enable debugging. From time to time, we get loaded our specific iFrame under Script Documents -> Windows Internet Explorer -> <our dashboard site> -> <set of Javascript files>.

Then after clicking through the client, our site is gone again and does not show up again. When it is up, we are enabled to set breakpoints into JavaScript framework files (such as bootstrap, jquery etc.) but breakpoints in our JavaScript code does not work.

Also we don't see main.js during debugging at all. We know this is JScript document. This problem is described here: community.m-files.com/index.php

How do you debug your UI extension apps? Any plans to stick to one scripting language and not to mix between JScript and JavaScript in future?

Dejan
Parents
  • Hi Dejan,

    We don't believe that we explicitly embed Internet Explorer; we embed the WebBrowser control that Microsoft provides. In practicality this is the Internet Explorer engine but, even if Microsoft stop using the legacy Internet Explorer standalone browser, this control will continue to be available.

    I know that Microsoft did say that they would look to replace the WebBrowser control with the Chrome-based Edge at some point in the future. My understanding is that this would be a different control, though ("WebBrowser2"?), that people could opt into using if they wanted to. However, I am unaware of the state of that development at Microsoft, and I do not believe that M-Files is currently actively developing anything that would change the above developer story.

    Regards,

    Craig.
Reply
  • Hi Dejan,

    We don't believe that we explicitly embed Internet Explorer; we embed the WebBrowser control that Microsoft provides. In practicality this is the Internet Explorer engine but, even if Microsoft stop using the legacy Internet Explorer standalone browser, this control will continue to be available.

    I know that Microsoft did say that they would look to replace the WebBrowser control with the Chrome-based Edge at some point in the future. My understanding is that this would be a different control, though ("WebBrowser2"?), that people could opt into using if they wanted to. However, I am unaware of the state of that development at Microsoft, and I do not believe that M-Files is currently actively developing anything that would change the above developer story.

    Regards,

    Craig.
Children
No Data