Comments
Sort by recent activity
It doesn't appear to be multi-threaded in that the method call is synchronous and will wait until the interop code returns. I wonder if the nature of COM messaging (way down deep it uses the old windows message--i.e. wndprocs and the like). I wonder if this is affecting it?
Should ANTS handle profiling COM interop (or any interop) for that matter? / comments
It doesn't appear to be multi-threaded in that the method call is synchronous and will wait until the interop code returns. I wonder if the nature of COM messaging (way down deep it uses the old w...
I finally got it working. I reinstalled .NET 1.1. (SP1) but that didn't help. After reading your description of what is going on, I checked my local 'hosts' file (\system32\drivers\etc\hosts) and noticed there was an additional mapping to 127.0.0.1 for an app I was debugging a long time ago.
There still was the:
127.0.0.1 localhost
entry, but apparently having this second mapping:
127.0.0.1 myapp.mycompany.com
didn't work well with ANTS. After removing the second entry, the profiler seems to work now.
Thank you for all your help! / comments
I finally got it working. I reinstalled .NET 1.1. (SP1) but that didn't help. After reading your description of what is going on, I checked my local 'hosts' file (\system32\drivers\etc\hosts) and...
I have Windows XP SP2 installed. The Windows Firewall is disabled, but I do get this audit entry in my security event log (it's reporting port 2478):
The Windows Firewall has detected an application listening for incoming traffic.
Name: ANTS Profiler
Path: C:\Program Files\Red Gate\ANTS Profiler\RedGate.Profiler.UI.exe
Process identifier: 2972
User account: tdietz
User domain: HUBBARDONE
Service: No
RPC server: No
IP version: IPv4
IP protocol: TCP
Port number: 2478
Allowed: Yes
User notified: No / comments
I have Windows XP SP2 installed. The Windows Firewall is disabled, but I do get this audit entry in my security event log (it's reporting port 2478):
The Windows Firewall has detected an applicati...
Sorry for the typos. To clarify.
I stopped the ANTS profiler service.
Netstat didn't find anything listening on 8087
I started the ANTS profiler service
Netstat found something listening on 8087. / comments
Sorry for the typos. To clarify.
I stopped the ANTS profiler service.
Netstat didn't find anything listening on 8087
I started the ANTS profiler service
Netstat found something listening on 8087.
No. The firewall is disabled via a company-security policy.
Is there anything I might need to set in IIS or ASP.NET's machine.config? It should be all stock configs right now. / comments
No. The firewall is disabled via a company-security policy.
Is there anything I might need to set in IIS or ASP.NET's machine.config? It should be all stock configs right now.
I checked everything and things look normal. It's just a normal .NET application running on localhost on port 80, i.e. http://localhost/myapp/
Going there in the browser (or VS.NET debugger) works great, never any problems.
If I try to run ANYTHING through ANTS (e.g. sample .NET applications) I get the same error as posted above. / comments
I checked everything and things look normal. It's just a normal .NET application running on localhost on port 80, i.e.http://localhost/myapp/
Going there in the browser (or VS.NET debugger) works ...
Yes, I just did this and it reports that it is "LISTENING"
TCP machinename:8307 machinename:0 LISTENING / comments
Yes, I just did this and it reports that it is "LISTENING"
TCP machinename:8307 machinename:0 LISTENING