Good luck with that. I've been coding C# a long time, and the two of them
(along with a few others) are enough to give somenome a complex! Some of the
people here are way to smart...
Agreed. There is such a thing as "thinking too much" or
"overengineering"!
XML is another of those "small, easy to master" topics, kind of like
Databases, Concurrency, and OO.
True, true. I just finished all I need to know (for now) in the book
by Wrox "Beginning C# 2005 Databases" by Karli Watson. Pretty good
stuff. The key is knowing when to use the visual tools to design a
query, and when to use a command (faster), and of course the interface
to the Visual Studio C# front end. Helps to know SQL, which I learned
in about a day. As for XML, if you stick to what is known as the
'forward stream' (non-tree, just moving forward in sequential fashion)
version, it's just like FileStream--plug and chug--the bit about
attributes versus elements is a bit confusing but largely a tempest/
teapot situation. Don't know much about Concurrency yet, but it seems
pretty simple--just stop one thread whenever you need another to catch
up, and so forth. OO is of course the base for all things, and it
does take a while to "think" in OO style, but to be honest, I find
that a lot of stuff that I and others write ends up really being
procedural stuff recast as OO. I mean, how often to you really use
polymorphism anyway? Not all that often.
Happy coding,
RL