[Gibbon1]

I've done some stuff in .net. One of the advantages is the learning curve is pretty fast. So it's not a huge investment.

The flip side is it seems a lot of .net jobs are sausage making. Not very much in the way of cutting edge or exciting stuff gets done in .net. Though too cutting edge often is crash and burn, where run of the mill projects can last years and years. (Don't knock a steady paycheck)

[gamechangr]

I know it's hard to say, but how fast is "the learning curve is pretty fast"? Would two months straight be enough to have a reasonable command (I get that it would be entry level at best)

[Gibbon1]

I would say two months straight of serious study and practice would be more than enough to solidly know your way around the language, .net libraries and tools.

Buy a good book.

I don't actually do client side (or server side stuff) as primary work. However .net is very useful for kicking out simple GUI based tools. If you want to do that, .net has the fastest learning curve end of story.

[gamechangr]

Thanks "Gibbon1" for avoiding the usual "10,000 hours" response. Upvoted!

I know it's hard to quantify. I have a friend who has offered to do a "8 week internal training program with me" if I commit to working with his company for one year.

I just wanted to hear someone objectively tell me that they thought that's doable first.