ExceptionReporter Forum Rss Feed

New Post: Joins Reporter projects

kiquenet — Tue, 29 Jan 2013 11:46:05 GMT

Why not join in one project: Exception Reporter and CrashReporter.Net ?

http://exceptionreporter.codeplex.com/

https://crashreporterdotnet.codeplex.com/

New Post: Email issues with mixed 32/64 bit environment

pandawood — Wed, 04 Jan 2012 01:44:52 GMT

Thanks, yeah I did notice that recently and didn't have the time to look at it but the research you've done there looks like the answer.

Looks like we can remove the call & maybe just confirm that other environments (32-bit/vista) don't have any negative effects.

New Post: Email issues with mixed 32/64 bit environment

philAtkin — Tue, 03 Jan 2012 16:47:32 GMT

I'm trying to use ExceptionReporter in a managed Win32 Application. I'm running on Win7/64, with 64-bit Office (including Outlook) installed and no 32-bit mail client (Win7 does not come with any mail client by default).

When I try to get ER to send an Email, I see an error "Microsoft Office Outlook / Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client". It turns out that Outlook is the default mail client.

The message box is shown during the (first) call to MAPILogon in Mapi.Logon(), and the error value returned is 0x80004005; session is left at null. However, the code continues and sends the email successfully. Looking at the documentation for MAPILogon here: http://msdn.microsoft.com/en-us/library/windows/desktop/dd296726(v=vs.85).aspx it seems that the function is deprecated.

I've disabled the call to mapi.Logon in MailSender.SendMapi and everything still seems to work fine. Since the call seems to be superfluous and troublesome, perhaps it would be better removed from the code?

New Post: ER in Addin VS 2008

alhambraeidos — Thu, 04 Aug 2011 09:01:23 GMT

Hi, I try use ER in my Addin VS 2008, but I get some errors.

[6532] Boolean ComprobarItemBajoSC(System.String)
[6532] en COMPANY.VSIntegration.TeamExplorerManager.TEManager.ComprobarItemBajoSC(String ficheroSolucion) en C:\TFS\pro\COMPANYTeam\Main\Public\COMPANYDevelopment\TeamExplorerManager\TEManager.cs:línea 691
[6532] en COMPANY.VSIntegration.COMPANYAddIn.Connect.EnvDTE.IDTCommandTarget.QueryStatus(String CmdName, vsCommandStatusTextWanted NeededText, vsCommandStatus& StatusOption, Object& CommandText) en C:\TFS\pro\COMPANYTeam\Main\Public\COMPANYDevelopment\COMPANYAddIn\Connect.CommandTarget.cs:línea 267
[6532] COMPANY.VSIntegration.COMPANYAddIn.Connect.TratamientoExcepcionEnConnect(Exception exc, String descripcion, Boolean modal) in C:\TFS\pro\COMPANYTeam\Main\Public\COMPANYDevelopment\COMPANYAddIn\Connect.CommandTarget.cs: line 557
[6532] COMPANY.VSIntegration.COMPANYAddIn.Connect.EnvDTE.IDTCommandTarget.QueryStatus(String CmdName, vsCommandStatusTextWanted NeededText, vsCommandStatus& StatusOption, Object& CommandText) in C:\TFS\pro\COMPANYTeam\Main\Public\COMPANYDevelopment\COMPANYAddIn\Connect.CommandTarget.cs: line 542
[6532] System.Windows.Forms.UnsafeNativeMethods+IMsoComponentManager.FOnComponentExitState(Int32 dwComponentID, Int32 uStateID, Int32 uContext, Int32 cpicmExclude, Int32 rgpicmExclude)
[6532] System.Windows.Forms.ComponentManagerProxy.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FOnComponentExitState(Int32 dwComponentID, Int32 uStateID, Int32 uContext, Int32 cpicmExclude, Int32 rgpicmExclude)
[6532] System.Windows.Forms.Application+ThreadContext.EndModalMessageLoop(ApplicationContext context)
[6532] System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
[6532] System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
[6532] System.Windows.Forms.Application.RunDialog(Form form)
[6532] System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
[6532] System.Windows.Forms.Form.ShowDialog()
[6532] ExceptionReporting.WinForms.Views.ExceptionReportView.ShowExceptionReport()
[6532] ExceptionReporting.ExceptionReporter.Show(Exception[] exceptions)
[6532] COMPANY.VSIntegration.COMPANYAddIn.Connect.TratamientoExcepcionEnConnect(Exception exc, String descripcion, Boolean modal) in C:\TFS\pro\COMPANYTeam\Main\Public\COMPANYDevelopment\COMPANYAddIn\Connect.CommandTarget.cs: line 573
[6532] COMPANY.VSIntegration.COMPANYAddIn.Connect.EnvDTE.IDTCommandTarget.QueryStatus(String CmdName, vsCommandStatusTextWanted NeededText, vsCommandStatus& StatusOption, Object& CommandText) in C:\TFS\pro\COMPANYTeam\Main\Public\COMPANYDevelopment\COMPANYAddIn\Connect.CommandTarget.cs: line 542

Perhaps not is possible using in Addin, or is required modifications about the source code

Thanks

New Post: Screenshot Capture with Reports

PandaWood — Thu, 07 Jul 2011 04:44:11 GMT

seankearon wrote:

What would be good is of the user could elect to send a screenshot. Currently, as I understand, the screenshot is either automatic or not. The screenshot may contain personal information that the user would not wish to share.

Yes, this concern applies when you choose to send an email, but even then, really only if you have configured SMTP for email.

That is because with MAPI (where it launches your native email program), the the screenshot is just 'attached', and a warning about the screenshot having been attached is included in the body of the email, encouraging you to delete it if it contains any private data.

New Post: CLR 2.0

PandaWood — Tue, 10 May 2011 10:56:27 GMT

One option is to download the 3rd drop - it was the last release based on the .NET2 framework.

There's a few features missing compared to the final version 2 but probably nothing to stop you from getting a lot of use out of it.

New Post: CLR 2.0

tanis2000 — Tue, 10 May 2011 07:51:16 GMT

Hi,

is there a downloadable binary version of Exception Reporter based off the .NET 2.0 CLR?

Thanks!

New Post: {"Error HRESULT E_FAIL has been returned from a call to a COM component."}

rpflughoeft — Wed, 04 May 2011 20:38:28 GMT

I wish I could help you. I ended up doing some redesign and the problem went away. Couldn't tell you for sure what fixed it.

New Post: {"Error HRESULT E_FAIL has been returned from a call to a COM component."}

jameswelle — Wed, 04 May 2011 18:54:06 GMT

I am seeing the same issue with IE9 installed on Windows 7 SP1 x64.

Was there every any resolution to this?

New Post: {"Error HRESULT E_FAIL has been returned from a call to a COM component."}

rpflughoeft — Mon, 31 Jan 2011 22:53:06 GMT

I have the following code

        private void CodeForExceptionReportEvent(object Sender, ExceptionEventArgs myArgs)
        {
            if (this.InvokeRequired)
            {
                ExceptionReportCallbackDelegate cb = new ExceptionReportCallbackDelegate(CodeForExceptionReportEvent);
                this.Invoke(cb, new object[] { Sender, myArgs });
            }
            else
            {
                myArgs.ExceptionReporter.Show(myArgs.CustomMessage, myArgs.Exception);
            }

On the highlighted line, I 'sometimes get this error'.

System.Runtime.InteropServices.COMException crossed a native/managed boundary Message=Error HRESULT E_FAIL has been returned from a call to a COM component. Source=System.Windows.Forms ErrorCode=-2147467259 StackTrace: at System.Windows.Forms.UnsafeNativeMethods.IWebBrowser2.Refresh() at System.Windows.Forms.WebBrowser.Refresh() InnerException:

Any thoughts?

New Post: Exception Reporter throwing exception, sometimes...

PandaWood — Sat, 04 Dec 2010 05:35:35 GMT

Is the ExceptionReport being called on the Background thread?

I always catch the exception on the thread and show the ExceptionReporter back on the UI thread. Otherwise weird things can happen.

New Post: Exception Reporter throwing exception, sometimes...

RefractedPaladin — Fri, 03 Dec 2010 16:08:17 GMT

Exception Reporter is working great for me. I am using it on a Winform project.

However, when I try and use it in one particular place it fails. It only reports this -->

Exception has been thrown by the target of an invocation.

The exception and innerexception are getting thrown appropriatly but when I get to the

ExceptionReporter.Show(exception)
portion I get the previously stated exception instead, like Exception Reporter itself has thrown it.

In the interest of 'full disclosure' the method it is doing this for is calling a database sync on a Background Worker.

Thoughts?

New Post: When can we expect the New Release?

PandaWood — Tue, 29 Jun 2010 04:24:48 GMT

There's a C# example in the Demo App (source code) It uses optional parameters.

private static void ShowMultipleExceptionReporter()
{
    Exception exception1 = null;
    Exception exception2 = null;
    try
    {
        SomeMethod();
    }
    catch (Exception exception)
    {
        exception1 = exception;
    }
    try
    {
        CallAnotherMethod();
    }
    catch (Exception exception)
    {
        exception2 = exception;
    }
    var exceptionReporter = new ExceptionReporter();

    exceptionReporter.ReadConfig();

    exceptionReporter.Show(exception1, exception2);
}

New Post: Exception Reporter en Español (Spanish)

edgartaor — Mon, 22 Mar 2010 02:45:43 GMT

Si, ya se que las etiquetas se pueden configurar con el xml de configuracion.... Pero me parecio util traducir el proyecto en si, listo para usarse en version español.

Pueden descargarlo desde aqui: http://www.mediafire.com/file/minzlageikx/ExceptionReporter_Español_Spanish.zip

Es el codigo fuente con el dll generado.

Saludos y espero que le sea de utilidad a alguien mas. ^__^

-------------------------------------------------------------------------------------------------------------------------------------

Yes, I know that labels can be configured with the configuration xml .... But I found it helpful to translate the project itself, ready for use in Spanish version.

You can download it from here: http://www.mediafire.com/file/minzlageikx/ExceptionReporter_Español_Spanish.zip

It is the source code with the generated dll.

Greetings and I hope it is helpful to someone else. ^ __ ^

New Post: When can we expect the New Release?

ashiswa — Fri, 11 Dec 2009 09:55:53 GMT

Thanks for your reply... Do you mean we can pass the exceptions array? but its not working see below.

        Dim vExp_Report As New ExceptionReporting.ExceptionReporter
        Dim vExp1(1) As Exception

        Try
            Dim i As Int16 = "Test"
        Catch ex1 As Exception
            vExp1(0) = ex1
        End Try

        Try
            Dim i As Int16 = "99999999999999999999999999999"
        Catch ex2 As Exception
            vExp1(1) = ex2
        End Try
        vExp_Report.Show(vExp1)

Please give me one example so that i can understand it better.

Thanks in Advance.

New Post: WPF Version?

abmv — Fri, 11 Dec 2009 07:22:39 GMT

I guess using the WinForm ExceptionReporter would work in a WPF app. I was only thinking in the terms of WPF.

Thanks for you reply regarding this matter. I hope you will be able to move it across to WPF. This component could be useful in both WPF and XBAP scenarios.

New Post: WPF Version?

PandaWood — Thu, 10 Dec 2009 23:21:45 GMT

Hi,

I'm currently using WinForms ExceptionReporter in a WPF app - which means it's still possible and completely functional as it is. Your question seems to infer that it's not possible, so that needs clearing up.

However, I would like to move it across to WPF to take full advantage of some WPF UI features.

New Post: When can we expect the New Release?

simoncropp — Thu, 10 Dec 2009 22:17:54 GMT

Ash

It does support multiple exceptions.

Here is the signature for ExceptionReporter.Show

     /// <summary>
       /// Show the ExceptionReport dialog
       /// </summary>
       /// <remarks>The <see cref="ExceptionReporter"/> will analyze the <see cref="Exception"/>s and
       /// create and show the report dialog.</remarks>
       /// <param name="exceptions">The <see cref="Exception"/>s to show.</param>
        public void Show(params Exception[] exceptions)

notice the exceptions parameter is an array

New Post: When can we expect the New Release?

ashiswa — Thu, 10 Dec 2009 13:39:22 GMT

Hi,

I was very delighted when I found this exception handling class, but unfortunately I will not be able to use it until it supports multiple errors...

I am hoping very much that you will release it very soon.

Ashi

New Post: WPF Version?

abmv — Sun, 01 Nov 2009 17:04:09 GMT

Please can you complete the WPF sample included version ? Thanks in advance for this ! It would be nice to have this in WPF since Windows7 has been release and comes with .net 3.5 sp1 and more are more people are trying to develop software in wpf this component would be defacto use full for error management since WPF does not have anything default.I hope you can find some time to close in on the WPF sample included version.