Comments
Sort by recent activity
I’m having the same problem profiling my asp.net application.
I’m running XP Pro and IIS 5.1
My aspnet_wp.exe process is running under a user name of ASPNET
My maching.config looks like this:
<processModel enable="true" timeout="Infinite" idleTimeout="Infinite" shutdownTimeout="0:00:05"
requestLimit="Infinite" requestQueueLimit="5000" restartQueueLimit="10" memoryLimit="60"
webGarden="false" cpuMask="0xffffffff" userName="machine" password="AutoGenerate" logLevel="Errors"
clientConnectedCheck="0:00:05" comAuthenticationLevel="Connect" comImpersonationLevel="Impersonate"
responseDeadlockInterval="00:03:00" maxWorkerThreads="20" maxIoThreads="20"/>
The profiler just sits there with the "Waiting for connection" message.
I did evaluate another profiler and I did run the regsvr32 command but still no luck.
I have loaded the latest VS 2005 beta which also installs the 2.0 framework, not sure if that matters or not.
Any ideas?
Thanks,
Ed [image] / comments
I’m having the same problem profiling my asp.net application.
I’m running XP Pro and IIS 5.1
My aspnet_wp.exe process is running under a user name of ASPNET
My maching.config looks like this:
<...