Comments
3 comments
-
Hi Adam,
I can't see a way of profiling a deployed clickonce application, you will probably be better off profiling it before it's been deployed.
If you use the "install on the computer" option, it should be a matter of opening the program shortcut and using the shortcut program name and arguments in the memory profiler's .NET desktop application settings.
If you make it so your users always have to go through the web browser to run the application, this is a bit more tricky. I have tried a few things to make it work -- one was the obvious:- program: c:\program files\internet explorer\iexplore.exe
- arguments: http://localhost/myapplication/my.application
Then the less obvious way of running ClickOnce that I got from reverse-engineering it:- program: c:\windows\system32\rundll32.exe
- arguments: dfshim,ShOpenVerbApplication http://localhost/myapplication/my.application
The ClickOnce app launches, but even with the "profile child processes" option turned on, neither ANTS Memory nor ANTS Performance profiler seem to pick up on the .NET app being run by ClickOnce.
I hope that someone more familiar with ClickOnce can chime in on this topic. :-) -
Sorry to be a nudge, has your firm found a solution? I think our issues are coming from something in the core of microsoft deployment and autoupdating, but I can't recreate the issue without the app being deployed via clickonce.
Thanks!
Adam -
Hi all,
I'm happy to say that you can successfully profile ClickOnce in ANTS Performance Profiler v6 using the earlier instructions:program: c:\windows\system32\rundll32.exe
arguments: dfshim,ShOpenVerbApplication http://localhost/myapplication/my.application
*where "http://localhost/myapplication/my.application" is the ClickOnce URL.*
Add comment
Please sign in to leave a comment.
Thanks!