>>I've had several classes on C#, probably about 3 of them, meaning 3 semesters, but that was a while back. I've never had any projects at any clients sites or on any projects using C#. I wonder if someone could advise me on what component to use for data access? Maybe component isn't the right word. Now, I am not a complete novice, but pretty close to it, so realize that I am also a bit rusty.
>
>Given that I know nothing about the type of environment you work in this may not be the best advice - but you could consider working with Entity Framework straightaway. It sits on top of ADO.NET so you can use it without really knowing ADO.NET at all. I note that Craig mentions Linq to SQL but that functionality is included in EF with Linq to Entities (but there's Entity SQL as well) and Linq to SQL isn't being moved forward so I don't feel there's much to be gained by exporing that path. I've only used EF with MSSQL so although there are providers for most other major backends I've no idea how well they work. Julia Lerman's 'Programming Entity Framework' is a good book - but a short play with the designer in VS should give you a basic feel of how it works.
>
>And just to stir things up a bit more, although you didn't ask, if you're looking at desktop apps then also consider WPF instead of WinForms :-}
>
>HTH,
>Viv

A bit off topic, Viv

I'm not into EF and WPF yet, just trying to find my way / get used to and discover

Some of the tough ones

(1) Finding a good name for classes/methods

(2) Namespaces. Name of them and how many
Too many = having a lot of 'using'

(3) Extension methods or static classes for a type of functionality
Too many extension methods clutter up intellisense
Putting things in static classes does not clutter up intellisense but you have to remember them

(4) Doing it right the first time (Namespace/ class/method names)
It takes time to figure out how to organize them. And the day after I may have changed my mind

(5) testing - a lot of time involved
I have found a way - may not the best one

All classes that need testing have a static method TestSuiteRun() which is conditionally compiled ( #define TESTSUITE in the project properties)
I have a static class TestSuite, with a Run() method that uses reflexion to find all the static TestSuiteRun() in all the classes and invoke them


Takes a bit of work to add it to the classes that need it - but then it's only once