debugging and tracing pagemethod calls wheres the cache?

Well I am not sure about the cacheing issue, my recommendation is to ctrl+F5 before retrying the webservice after it has been changed.

As for debugging, The reason maybe with visual web developer. What you can do, if you just want to write out to a debug window is do downlaod DebugView (@.http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx) and then add debug statements to the code.

System.Diagnostics.Debug.WriteLine("Hello World!")

This will write the debug info to DebugView (make sure it is running when the app runs, and that debug is set to true in the web.config).

Hope this helps

-Alan

1. Pls make sure your not running in "release" mode.
2. Are you calling the page method from a separate js file, in this there might be a chance the js file is cached.

I would also love to see the code.

Thanks for your help - the tool below helped me get to the root cause of my problem - a great find. thanks

aquillin:

As for debugging, The reason maybe with visual web developer. What you can do, if you just want to write out to a debug window is do downlaod DebugView (@.http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx) and then add debug statements to the code.

System.Diagnostics.Debug.WriteLine("Hello World!")