C#

ForkOffandDie wrote:

if calling Dispose() results in an implicit call to Close()

try
{
    if (table != null)
    {
        OleDbConnection connection;
        try
        {
            connection = new OleDbConnection();
            connection.Open();

            OleDbCommand command;
            try
            {
                command = connection.CreateCommand();
                command.CommandText = "SELECT obj From " + table.Alias;

                OleDbDataReader reader;
                try
                {
                    reader = command.ExecuteReader();
                    while (reader.Read())
                    {
                        container.Add(new Feature((xx)reader.Getxx(0)));
                    }
                }
                finally
                {
                    if (reader != null)
                    {
                        ((IDisposable)reader).Dispose();
                    }
                }
            }
            finally
            {
                if (command != null)
                {
                    ((IDisposable)command).Dispose();
                }
            }
        }
        finally
        {
            if (connection != null)
            {
                ((IDisposable)connection).Dispose();
            }
        }
    }
}
catch (Exception)
{
    MessageBox.Show("There was a GPS Error");
}

1. The runtime searches the array for the first protected block that:
   
   • Protects a region that includes the currently executing instruction, and
     
   • Contains an exception handler or contains a filter that handles the exception.
     
   
   
2. If a match occurs, the runtime creates an Exception object that describes the exception. The runtime then executes all finally or fault statements between the statement where the exception occurred and the statement handling the exception. Note that the order of exception handlers is important: the innermost exception handler is evaluated first. Also note that exception handlers can access the local variables and local memory of the routine that catches the exception, but any intermediate values at the time the exception is thrown are lost.
   
   
   If no match occurs in the current method, the runtime searches each caller of the current method, and it continues this path all the way up the stack. If no caller has a match, the runtime allows the debugger to access the exception. If the debugger does not attach to the exception, the runtime raises the UnhandledException event. If there are no listeners for the UnhandledException event, the runtime dumps a stack trace and ends the program.

ForkOffandDie wrote:

What would have priority over a thrown exception such that it HAD to process before a catch was allowed to handle the Exception?

Pete O`Hanlon wrote:

ms.Position = 0;

Luc Pattyn wrote:

Hi,

AFAIK an RTB is capable of showing an RTF file, which you can generate with either an RTB or
with Wordpad. An MS Word document (.doc) can not be loaded into an RTB.

System.Security.SecurityException wurde nicht behandelt.<br />
  Message="Fehler bei der Anforderung des Berechtigungstyps System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089."<br />
  Source="System"<br />
  StackTrace:<br />
       bei System.ComponentModel.ReflectPropertyDescriptor.SetValue(Object component, Object value)<br />
       bei System.Windows.Forms.RadioButton.PerformAutoUpdates(Boolean tabbedInto)<br />
       bei System.Windows.Forms.RadioButton.set_Checked(Boolean value)<br />
       bei System.Windows.Forms.RadioButton.OnClick(EventArgs e)<br />
       bei System.Windows.Forms.RadioButton.OnMouseUp(MouseEventArgs mevent)<br />
       bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)<br />
       bei System.Windows.Forms.Control.WndProc(Message& m)<br />
       bei System.Windows.Forms.ButtonBase.WndProc(Message& m)<br />
       bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)<br />
       bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)<br />
       bei System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)<br />
       bei System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)<br />
       bei System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)<br />
       bei System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)<br />
       bei System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)<br />
       bei System.Windows.Forms.Application.Run(Form mainForm)<br />
       bei CSharpImgPT.Program.Main()<br />
       bei System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)<br />
       bei System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)<br />
       bei Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()<br />
       bei System.Threading.ThreadHelper.ThreadStart_Context(Object state)<br />
       bei System.Threading.ExecutionContext.runTryCode(Object userData)<br />
       bei System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)<br />
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)<br />
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)<br />
       bei System.Threading.ThreadHelper.ThreadStart()