Well, if you've been following the MS official DBA path, they've split it into three paths: DB Admin, DB Developer, DB Knowledge Worker (Bus Intel, reports, OLAP type stuff).
What do you like to do? Do you like the server administration? If so, concentrate on T-SQL, WMI, VBScript, maybe some VB.Net. If you like to write code, but don't want to develop front-end or even middle-level components with C#/VB, consider buckling down on the T-SQL and learning how to create stored procs, triggers, design databases, etc. If you like writing reports and/or analyzing data, look at Reporting Services, Analysis Services, Integration Services/DTS, etc.
However, if you really want to learn coding, I would look at what type of code you want to write. C# probably has a lot of growth. VB.Net is okay, but I see more trends towards C# in the long run. ASP.Net will get you started with web programming. Web Services are growing right now from what I can see.
The question really comes back to you and what you want to do. While I believe that MS is simplifying a lot of the administration tasks to the point where you don't have to worry about them as much, that means that you have more to plan. Database Mirroring? Replication? Backups? Disaster Recovery? Snapshots? Performance? Baselines? Sure there are tools for a lot of those, but you need to know what's best for the appropriate scenario. (This is a Great solution. This is a Good solution. .... Someone tell me those answers have been dropped from the SQL exams. 🙂
There are lots of options out there. If you give us some idea of where you want to be, maybe we can give some more directed advice. After all, becoming a VB.Net programmer when you hate to write code would not make for a good long-term (or even short-term) career. Same for Production DBA if you don't like doing those tasks (or bus-driver or mail carrier or ....).