1)
Failure to catch exceptions period. There is no compile-time catch-block
validation as in Java.
The antithesis to this is catching too many exceptions:
try {
...
} catch(Exception) {}
is usually a bad thing. Especially in DLLs.
2)
Changing the value of a public constant in a DLL.
Richard
> -----Original Message-----
> From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of
> John Lam
> Sent: 24 May 2002 01:01
> To: [EMAIL PROTECTED]
> Subject: [DOTNET] What's your vote for a top-10 list of most common
> errors made be .NET devs?
>
>
> My vote is leaking ADO.NET database connections. My gut feel is that ADO
> devs who are used to deterministic destruction of their ADO connection
> objects will find it difficult (at first) to write the appropriate try
> ... finally blocks *everywhere* in their code to handle the cases where
> the methods within the try {} block throw exceptions.
>
> What other errors have folks seen based on their own (or others)
> experiences?
>
> Has someone attempted to assemble a FAQ along these lines already?
>
> Thanks,
>
> -John
> http://www.iunknown.com
>
> You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
> subscribe to other DevelopMentor lists at http://discuss.develop.com.
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
