>Not necessarily removed (in fact I assume not) but only there for classic ASP compatibility and not good practice in ASP.NET

Well, classic is gone since a very long time. So, I have notes on it and when time comes, I'll try to update the code.

>If your problem was mixed up with Response.Redirect then the suggested method seems to be to call Response.Redirect() with the second parameter 'false' (which suppresses the internal call to Response.End()) followed by a CompleteRequest()

Thanks