See hidden discussions | Win great prizes | Get free support
If you (like me) are still in a .NET 2.0
The biggest problem being we have to target the 2.0 framework.
I've been there. Worked for a company where we had no time to work on the new tech... and did most of the work in stored procs (this is mostly the case in Web environments). While it's essential that you have an in-depth knowledge of the c# language... don't think that that stops at for loops. FarligOpptreden refers to the "skill of a dedicated C# developer". In my view that is knowing the full tool set.
The point that i'd like to make is that even if you don't need to use the new stuff now, you probably will have to at some point (only, you might not know that it will help you because you don't know its strong and weak points).
When you sit around a boardroom table (or in-front of a client), and they ask you to design a long running workflow... do you want to leave it to then to find out whether WF could have saved you weeks?
The investigation alone will take you weeks... time that you are not likely to waste. You might decide it's a waste of time and put in your own workflow, only to hassle through the same stuff the M$ team worked through when building workflow. Or, you might decide to take the leap then... only to find WF doesn't provide you the visibility that you need in tracking your WF tasks.
You can't make good decisions on which tech to use if you don't know them.
FarligOpptreden, while I understand your argument (worked on stored proc intensive systems) it doesn't hold too much water. Stored procedures are great... but to stick your entire system in your database makes debugging difficult, and scalability a nightmare.
Anyway, that's my POV. Use it, don't use it.