DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: Wed, 01 Aug 2007 14:12:54 -0700,    posted on: microsoft.public.dotnet.internationalization        back       

Thread Index
  1    unknown


Forcing exception messages to English   
I have a C# application that installs a custom handler for
AppDomain.CurrentDomain.UnhandledException that will grab a stack
trace and the text of the exception.  It then launches a separate app
to upload this information through a web form to a bug tracking
system, so that the app developers can track down and fix the issue.

This works great for most users, however some are in non-English
cultures and the exception message is worthless to our (english-only)
developers.  Is there a way to have the exceptions put into the
invariant culture so that

.NET Exception: オブジェクト参照がオブジェクト
インスタンスに設定されていません。

instead becomes something that is understandable?  At this point such
a bug reporting system becomes basically worthless for users that are
not in English-speaking locales.  As far as I can tell, this message
is coming from the .NET framework and is not one we are throwing.  The
stack trace tells us which function it was in, but does not give any
more granularity than that.  I cannot even tell what class of
exception it is as the reporting function is not a catch() but a
handler which takes a base Exception parameter.
Date:Wed, 01 Aug 2007 14:12:54 -0700   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us