>I have one pet peeve with .NET (so far). I have a business object class library that contains an "entity" class for a SQL Server table named "Event". I went through a moderate amount of trouble to automate creation of the entity class definitions for an entire database, and one of the first issues was enclosing all class names and property names in brackets [ ] so I wouldn't run into problems with keywords that happen to match class or property names. Everything was rosy until I added a Web Reference to a Web Service that contained the class definition. It seems that the Reference.vb generator does not include the brackets, which causes a compilation error after I update the Web Reference.
>
>Does anyone else have any pet peeves that they would like to share?

Keith;

I have my share and here is a simple one: In HTML you use the input tag and the property “value”, while using .NET “Value” is called “Text”.

Changing the terms keeps you on your toes if that is where you like to be! :)

One nice thing about these differences is that you get burned once and that is all it takes to remember! :)

Tom