General good practice in VB.Net, is there any?

I just wish to know good practices in VB.Net, could anybody share some?

That's a pretty general question, and it's also a bit subjective, as evidenced by some of the debates on this forum. There are certain "good practices" that ignoring can cause genuine issues, like not calling Dispose on every object that has that method when you're finished with it, and there are others that are just a matter of creating clearer code, like specifying the loop counter or element after the Next keyword.

As I mentioned, it would be really "General." :)

I find this link valuable that I want to share it... :)

Here are some links some people may find interesting.

ADO.NET Best Practices

Some .NET best practices books.

ASP.NET Best Practices

Is calling dispose like making the object equal to nothing?