_Black_Здравствуйте, _Black_, Вы писали:

_B_>какая-то беда с ним ...
_B_>пытался оттестировать логирование всех ошибок,
_B_>для этого поместил код, который их логгирует в global.asax.cs в метод Application_Error
_B_>в веб-методе пишу throw new Exception ("bla-bla-bla"), но почему-то в глобальный обработчик не попадаю :(
_B_>почему так — кто знает?

в догонку, — если делаю throw new Exception ("bla-bla-bla") в самом global.asax (e.g. Application_Start), тогда все срабатывает как надо.
http://msdn2.microsoft.com/en-us/library/24395wz3.aspx

Цитата:
...
It is better to use Try/Catch blocks around any code that is subject to errors instead of relying on a global error handler.

An error handler that is defined in the Global.asax file will only catch errors that occur during processing of requests by the ASP.NET runtime. For example, it will catch the error if a user requests an .aspx file that does not occur in your application. However, it does not catch the error if a user requests a nonexistent .htm file. For non-ASP.NET errors, you can create a custom handler in Internet Information Services (IIS). The custom handler will also not be called for server-level errors.

You cannot directly output error information for requests from the Global.asax file; you must transfer control to another page, typically a Web Forms page. When transferring control to another page, use Transfer method. This preserves the current context so that you can get error information from the GetLastError method.

After handling an error, you must clear it by calling the ClearError method of the Server object (HttpServerUtility class).
...