Current filter:
                                You should refresh the page.
                                  • Description:
                                    What should I do to inform you about a problem, which occurs at runtime and which I cannot reproduce step-by-step?

                                    Please utilize the approach described in the How to: Break When an Exception is Thrown MSDN article to catch user handled exceptions.
                                    In short, required steps are:

                                    1. In the VS Tools | Options... dialog go to the Debugging node and uncheck the Enable Just My Code (Managed Only) check box.
                                    2. Select the Debug | Exceptions... menu item or press Ctrl+Alt+E. The Exceptions dialog will appear.
                                    3. Select the "Common Language Runtime Exceptions" item.
                                    4. Reproduce the problem and open the Call Stack window (Debug | Windows | Call Stack).
                                    5. Select all text in the Call Stack window. Press Ctrl+C to copy it to the clipboard.
                                    6. Send us the stack trace.

                                    When an exception relates to cross-thread communications, it is necessary to analyze stack traces in all threads. To obtain this information, click the Debug | Windows | Threads menu item. In the Threads window, click the "Expand callstacks" item in the toolbar, select all lines and copy them.

                                    If the exception occurs on your end-user's machine (or anytime when it is not possible to attach a debugger to the application to obtain the call stack), you can handle the AppDomain.FirstChanceException event and save the exception's call stack programmatically. Here is a simple code snippet that illustrates how to save the log file to an end-user's desktop.

                                    AppDomain.CurrentDomain.FirstChanceException += (sender, e) => { System.Text.StringBuilder msg = new System.Text.StringBuilder(); msg.AppendLine(e.Exception.GetType().FullName); msg.AppendLine(e.Exception.Message); System.Diagnostics.StackTrace st = new System.Diagnostics.StackTrace(); msg.AppendLine(st.ToString()); msg.AppendLine(); String desktopPath = Environment.GetFolderPath(Environment.SpecialFolder.Desktop); string logFilePath = String.Format("{0}\\{1}",desktopPath,"logfile.txt"); System.IO.File.AppendAllText(logFilePath, msg.ToString()); };
                                    AddHandler AppDomain.CurrentDomain.FirstChanceException, Sub(sender, e) Dim msg As New System.Text.StringBuilder() msg.AppendLine(e.Exception.GetType().FullName) msg.AppendLine(e.Exception.Message) Dim st As New System.Diagnostics.StackTrace() msg.AppendLine(st.ToString()) msg.AppendLine() Dim desktopPath As String = Environment.GetFolderPath(Environment.SpecialFolder.Desktop) Dim logFilePath As String = String.Format("{0}\{1}",desktopPath,"logfile.txt") System.IO.File.AppendAllText(logFilePath, msg.ToString()) End Sub

                                    The best place for this code is the Main  method in your application.
                                    See Also:
                                    How to investigate the issue and determine why it occurs in your project
                                    How to obtain a design-time exception call stack
                                    Collecting a call stack to track down the cause of VS crash or freeze issues

                                • Guido Geurts 03.09.2018

                                  When using the FirstChanceException  method, do I still need to do all the steps described above ?

                                • Serge (DevExpress Support) 03.12.2018

                                  Hi Guido,
                                  Those steps are intended for design time, when you need to obtain a call stack from within your Visual Studio. The FirstChanceException  method is executed at runtime in your application's code, so they are unnecessary.

                                • Levente Botha 09.25.2018

                                  Hi, thank you for the detailed help and info.

                                  The exceptions are the following:

                                  Additional information: The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator.
                                  Exception thrown: 'DevExpress.Xpo.DB.Exceptions.SqlExecutionErrorException' in DevExpress.Data.v18.1.dll
                                  Additional information: Executing Sql 'select top 201 N0."F_ReceiptInfoID" from "dbo"."T_ReceiptInfo" N0

                                  The call stack is empty.

                                • Levente Botha 09.25.2018

                                  Changed to varchar, the problem ha gone. Thank you again!

                                • Uriah (DevExpress Support) 09.26.2018

                                  Hi Levente,

                                  I am happy to hear that this information helped you. If you have further questions, feel free to submit a new ticket and describe steps to reproduce this error, or add this information to your existing ticket if you already created such.

                                  >> The call stack is empty.

                                  This can be caused by the Just My Code option. Next time you research another issue using this approach, make sure that you disabled the Just My Code option.

                                0 Solutions

                                Creation Date Importance Sort by