>>No, that's what it seems like (and why I just used Response.CompleteRequest).
>>If you actually follow the CompleteRequest link it goes here : http://msdn.microsoft.com/en-us/library/system.web.httpapplication.completerequest.aspx
>
>Very well, I will then have to recheck on this. So, from what you say, Reponse.End() should no longer being used because its support will be removed at one point or another.

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

> The CompleteRequest() method should then be used.

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() e.g.:

Response.Redirect("somepage.aspx",false);
HttpContext.Current.ApplicationInstance.CompleteRequest();