Well that's awesome - I loved your article and I'm a total nut about the kind of stuff your writing articles about. I mentioned how Intel is a good source for both hardware and chip set programming reference manuals and that last I knew they still shipped them free to developers to encourage intel chip use. also there is a great (dated but good) 386 protected architecture book I used to have from SAMS I think that helped me wrap my head around the segment descriptors, memory model choices.. made me wish Novell didn't lose focus - their network server had a FAST configuration... all they needed was a gui LOL. I'm also following a freepascal OS effort - totally written in Freepascal - a departure from the C/C++ GNU stuff - which all rocks - just freepascal has alot to offer too, especially on intel because of how it uses the stack for calls - but I digress. Keep up the good work on the articles. (it was probably my browser or something) --Jason Know way too many languages... master of none!

Naahh... if it pays the bills - or some of them at least - you're not necessarily in the wrong business. I recently went to an oral surgeon for my teeth, and THAT my friend is a racket! We might all be in the wrong business. But back to .Net and Microsoft and whatever - there is a lot of good in that .Net stuff, I've written a lot of code in it - I prefer C# out of the language posse... To answer the original poster... if you WANT to invest in Microsoft Technology, by all means get good on the stuff not out yet, you'll be up to speed when it's released... and you can be sure it will be supported at least a year thereafter (historically speaking)... most likely 2 to 3 years... but .Net 3 hasn't been out that long - and they are already replacing it but in their defense, you still can get .Net 1.0 to run on today's platforms. THAT PART IS GOOD... the code RUNS GOOD (not lightning fast but good) and in all .net you need to obfusciate your code for commercial releases. --Jason Know way too many languages... master of none!