Ill be perfectly honest I am not super familiar with how dotTrace works, I recently downloaded the try in hopes of it helping to identify my performance issues I am having. I have written a application in C# and .NET 3.5 utilizing the SCSF Framework. It was designed to work on a full pc or laptop. However recently it has been requested to run on a netbook that has a measly 600mhz Atom processor. Pretty much everything runs slower which i expected, but there a are a few places where loading a screen takes 30 seconds or longer. My hope was to use dotTrace to help me identify where the pain points are. I tried using it locally and Im having a little trouble reading the output of dotTrace and identifiying exactly where the problems are, and is there a way for me to monitor a compiled assembly on a remote machine? Thanks!
It's posiible - dotTrace 4.0 works on remote computer. You need make some stepes for it:
1. Create folder on remote computer
2. Copy following files (build version <= 4.0.506) to remote folder:
2. Run on remote comnputer "%WinDir%\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe" /i JetBrains.Profiler.dotTrace.Agent.Remote.exe
3. Go to "Services"on remote comnputer, find "JetBrains Profiler Remote Agent" and assign administrator user right for this service (see Properties | Log On)
4. Go to "Computer Management" on remote comnputer, choose "Local User and Groups | Groups" and add new group with name "JetBrains Profiler Remote Agent".
5. Add set of users who will have the access to this remoting profiling service.
6. Go to "Windows Firewall" on remote comnputer and open port 9000 for incoming connections and allow all outgoing connections.
7. Start "JetBrains Profiler Remote Agent" service. Check that "C:\JetBrains.Profiler.dotTrace.Agent.Remote.log" will be created.
8. Go to "Windows Firewall" on local comnputer, enable all incoming connections for "dotTrace.exe" & "JetBrains.Profiler.dotTrace.ExternalLauncherProcess.exe".
9. Go to local computer and start dotTrace, press "Profile Advanced", choose "Remote Computer", enter parameters and press "Connect".
10. You are success if you see options dialog.
WBR, Mikhail Pilin
The remote agent has been totally redesigned (from build 4.0.508):
1. Changed list of files which you need to copy to the remote computer:
I am trying to profile an IIS application via the remote agent.
I am running it with administrator priviledges on the remote machine using the /console switch.
After adding the connection options I get a "Connection failed: No such host is known" while the agent says: "Authenticated as passphrase match".
Both firewalls are off and I rdp to the remote machine.
Current remote agent implementation requires both hosts have be able to connect to each other. This isn't a good idea and we are planing to redesign remote agent.
Could you send me logs (zip all files from "%temp%\JetLogs") from both computers?
WBR, MIkhail Pilin
Thanks very much for your help, unfortunately my machine is inside our company network and cannot be reached from the outside, so I am sure that is the problem.
I worked around the problem via recording the snapshot on the remote machine and copying it on mine.
I really look forward to the new version, keep up the good job:)
Basically this makes remote tracing 'useless' for complex network setups.
We have a bridge-VPN to our two data centers and there is no routing from the servers back to the dev-PCs.
There are no firewalls running, the test servers are reachable, but we still get the 'No such host is known' error.
I hope this gets fixed in the next version!
I find that I am unable to connect to a remote machine at all through a VPN. dotTrace 4.0, with firewalls all dissabled. The machine is pingable, remote desktop, and windows shares all work fine.