#64- Can't profile an ASP.Net application
http://www.intellij.net/tracker/netprofiler/viewSCR?publicId=64
Hi,
When I click on stop the IISReset.exe window executes and finishes. I then get a message box:
Wrong Snapshot
Can no load needed snapshot
Best regards
Steve
Attachment(s):
Bug - build 100.gif
Please sign in to leave a comment.
This is exactly the same as : http://www.intellij.net/forums/thread.jsp?forum=53&thread=124467&tstart=0&trange=15
Regards,
Mark Monster
Hi Mark,
I thought it might be. Though the details were a little sketchy in the forum and I couldn't find the bug in the bug database.
So I posted all the detail I had - glad it's fixed :)
Best regards
Steve
Hi,
I'm afraid that the problem still persists in build 101.
Best regards
Steve
Hi,
Build 102 is a little different. No error this time, I get a box while the browser running with two buttons 'Start' (which is greyed out) and a 'Kill' button.
Loading a couple of pages and hitting Kill does not produce any results (or errors).
Best regards
Steve
Build 103 doesn't start IISReset at all...I get an immediate error message:
Wrong Application
Can not start profiling
Best regards
Steve
Hi Mike,
Is there anything else you need me to do?
Best regards
Steve
http://www.intellij.net/tracker/netprofiler/viewSCR?publicId=64
State of this request was changed from "Submitted" to "Open"
Priority: High
Planned for version: 1.0
Steve,
Can you take the latest build and try to profile a simplest application using it (create a web form with a button and place it to the default IIS place)?
Hi Oleg,
I created a new web application with a single web form and a button on it. When I click on Stop IIS and Get Snapshot it restarts the services then completes with the message box.
JetBrains .NET Profiler
-
Profiler agent has not been initialized.
-
OK
-
The download was 109 but the application thinks that it's build 110.
I tried this with 'start taking measurements immediately' on and off.
Best regards
Steve
http://www.intellij.net/tracker/netprofiler/viewSCR?publicId=64
State of this request was changed from "Open" to "Fixed"
Fixed in build: 111