C# Listen code trouble in BeginInvoke

[leandro5]

Closed this

[Mikesch01]

This code has so many flaws.

- Never run logic in a catch
- NEVER RUN ASNYC CODE IN A CATCH
- Never let a catch empty
- Use while instead of goto-loops
- Remove unnecessary code

- Use english as your coding language
- Use SOLID principle
- Use clean code

This code is unreadable.

[leandro5]

Originally Posted by Mikesch01

This code has so many flaws.

- Never run logic in a catch
- NEVER RUN ASNYC CODE IN A CATCH
- Never let a catch empty
- Use while instead of goto-loops
- Remove unnecessary code

- Use english as your coding language
- Use SOLID principle
- Use clean code

This code is unreadable.

Thanks for the feedback and seems i found where was the problemwas calling endinvoke inside ProcederAceitar i just changed it and now call it's after result where begininvoke is called:

                if (OnAceitar != null)
                {
                    IAsyncResult result;
                    Console.WriteLine("OnAceitar != null client: {0} Handle: {1}", handler.RemoteEndPoint, handler.Handle);
                    result = OnAceitar.BeginInvoke(client, new AsyncCallback(ProcederAceitar), client);
                    OnAceitar.EndInvoke(result);
                    Console.WriteLine("iAsyncResult OnAceitar.BeginInvoke: " + result.AsyncState);
                }

        private void ProcederAceitar(IAsyncResult ar)
        {
            if (Fexando)
            {
                Console.WriteLine("ProcederAceitar Fexando igual a true");
                return;
            }

            //OnAceitar.EndInvoke(ar);

[tehpwnerer69]

Originally Posted by Mikesch01

- Never let a catch empty

I gotta disagree with you here, especially when handling procedures that will always throw off an error and you simply want to catch it and nothing more

E.g. attempting a ParseFloat inside of a try catch statement, inside of a boolean.

If you know what the exception is, you know it's not harmful and that it's not just floating around in memory, then what harm can this really do? Nothing and it is common practice for professional coders to
catch(Exception e){}//and thats all
Because why handle something that need not be handled?

So I disagree on this key point here
Keep in mind I didn't see the code posted