Profile JS Code in WebBrowser Control

Question

0.00/5 (No votes)

See more:

, +

Hi,

I'm looking for a JavaScript profiling tool which is external to the browser.

I have a project where there's a website which interacts with an object for scripting on the C# side via a number of JavaScript scripts.

This is done via the .Net WebBrowser control and as such I do not have access to the traditional developer tools one now expects from a browser.

I'm sure I've seen tools which run external to the browser and provide performance profiling information but I can't remember what it is.

I know there are libraries which can be added to the HTML content. I'm trying to avoid this to limit the impact on performance whilst profiling.

Any help appreciated.

Regards,

Steve

Posted 28-Feb-15 12:50pm

Stephen Hewison

Add a Solution

Comments

Sergey Alexandrovich Kryukov 28-Feb-15 23:49pm

I'm afraid some profiler would be hard to create, because JavaScript implementations sit inside the browsers. Hooking it up the way needed for profiling means being the insider of the browser and, hence, operate only with one specific browser vendor. Maybe, I'm missing something, but this is how I understand it at the moment.

That said, "libraries which can be added to the HTML content" look pretty much unavoidable. Perhaps you have to think at the workflow when you add such libraries during development and eventually remove them before deployment of production version. Just the idea...

—SA

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)