Hello,
with ASP.NET 2.0 Ajax every unexpected error is managed client-side with a
popup that reports the error to the user. In ASP.NET 3.5 this behavor has
been changed: how can I have a similar behavor? I'd like that every
exception raised from ASP.NET runtime during an asyncpostback is managed in
client side with a popup that reports the error message.
thanks
I belive you have an event you can subscribe to.. So every time error
happens your Javascript function is called.
George.
"Trapulo"
news:utOPOKwnIHA.5268@TK2MSFTNGP05.phx.gbl...
> Hello,
> with ASP.NET 2.0 Ajax every unexpected error is managed client-side with a
> popup that reports the error to the user. In ASP.NET 3.5 this behavor has
> been changed: how can I have a similar behavor? I'd like that every
> exception raised from ASP.NET runtime during an asyncpostback is managed
> in client side with a popup that reports the error message.
>
> thanks
>
>
Hi Trapulo,
As for ASP.NET ajax, you can register the event hander for client-side load
events. One of them is "EndRequest" in which we can detect whether there is
any error during the AJAX request processing. Here is web article mentioned
this:
##How to improve ASP.NET AJAX error handling
http://encosia.com/2007/07/18/how-to-improve-aspnet-ajax-err or-handling/
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx .
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Trapulo"
>Subject: ASP.NET 3.5 AJAX and default error handler
>Date: Tue, 15 Apr 2008 16:11:08 +0200
>Hello,
>with ASP.NET 2.0 Ajax every unexpected error is managed client-side with a
>popup that reports the error to the user. In ASP.NET 3.5 this behavor has
>been changed: how can I have a similar behavor? I'd like that every
>exception raised from ASP.NET runtime during an asyncpostback is managed
in
>client side with a popup that reports the error message.
>
>thanks
>
>
>
Hi Trapulo,
In addition to handling errors in Javascript, you can also register an
event handler with the ScriptManager's OnAsyncPostBackError delegate.
For an example for each methods, I suggest you check out
http://msdn2.microsoft.com/en-us/library/bb398934.aspx.
==========
Regards
Steve
www.stkomp.com
Trapulo wrote:
> Hello,
> with ASP.NET 2.0 Ajax every unexpected error is managed client-side with a
> popup that reports the error to the user. In ASP.NET 3.5 this behavor has
> been changed: how can I have a similar behavor? I'd like that every
> exception raised from ASP.NET runtime during an asyncpostback is managed in
> client side with a popup that reports the error message.
>
> thanks
This is interesting, thanks, but I'm not sure about this. The page you
refers says:
"the default behavior is that a browser message box is displayed with an
error message"
this is true in ASP.NET 2, but with ASP.NET 3.5 nothing is displaye when an
error occurs. Why? is this a problem in my application? I think it's by
design..
I'd like to manage errors with custom UI elements as your suggestion or
Steven's one says, but first of all I need to have the standard behavor:
when an exeption is raised, a message box is displayed to the user. Whitout
to write any specific code. How can I have this in ASP.NET 3.5?
thanks
news:cacffc84-c773-4fa8-af3a-28055a94f3a5@e67g2000hsa.google groups.com...
> Hi Trapulo,
>
> In addition to handling errors in Javascript, you can also register an
> event handler with the ScriptManager's OnAsyncPostBackError delegate.
> For an example for each methods, I suggest you check out
> http://msdn2.microsoft.com/en-us/library/bb398934.aspx.
>
> ==========
> Regards
> Steve
> www.stkomp.com
>
> Trapulo wrote:
>> Hello,
>> with ASP.NET 2.0 Ajax every unexpected error is managed client-side with
>> a
>> popup that reports the error to the user. In ASP.NET 3.5 this behavor has
>> been changed: how can I have a similar behavor? I'd like that every
>> exception raised from ASP.NET runtime during an asyncpostback is managed
>> in
>> client side with a popup that reports the error message.
>>
>> thanks
Steven,
the improvement you suggest is interesting. But before to create custom
client side code, I'd like to re-enable the standard behavor I had working
with ASP.NET 2.0: when an error occurs, a message box is displayed with
exception's message. i don't have this starting from ASP.NET 3.5. Is this
possible? Is there some error in my applications, if I haven't this behavor
more?
thanks
"Steven Cheng [MSFT]"
news:TzH2rm4nIHA.8872@TK2MSFTNGHUB02.phx.gbl...
> Hi Trapulo,
>
> As for ASP.NET ajax, you can register the event hander for client-side
> load
> events. One of them is "EndRequest" in which we can detect whether there
> is
> any error during the AJAX request processing. Here is web article
> mentioned
> this:
>
> ##How to improve ASP.NET AJAX error handling
> http://encosia.com/2007/07/18/how-to-improve-aspnet-ajax-err or-handling/
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
> Delighting our customers is our #1 priority. We welcome your comments and
> suggestions about how we can improve the support we provide to you. Please
> feel free to let my manager know what you think of the level of service
> provided. You can send feedback directly to my manager at:
> msdnmg@microsoft.com.
>
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx .
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> --------------------
>>From: "Trapulo"
>>Subject: ASP.NET 3.5 AJAX and default error handler
>>Date: Tue, 15 Apr 2008 16:11:08 +0200
>
>>Hello,
>>with ASP.NET 2.0 Ajax every unexpected error is managed client-side with a
>>popup that reports the error to the user. In ASP.NET 3.5 this behavor has
>>been changed: how can I have a similar behavor? I'd like that every
>>exception raised from ASP.NET runtime during an asyncpostback is managed
> in
>>client side with a popup that reports the error message.
>>
>>thanks
>>
>>
>>
>