Ive been using VB.net off and on for a year now, but I havent inhaled. VB.net seems more 'OLE'ish than vb6 to begin with, but I personally have no use for it at this time.
Besides, I dont need the sw/.net addin wizards, I have my own VB6 vers <grin>
VB.net is a lot more structured vs. VB6. More along the lines of C++.
The only drawback at this time is that VB applications created with .net will not run on a VB6 machine unless the MS-VB translator download is installed.
Remember...
"If you don't use your head,
your going to have to use your feet."
I have been using VB.NET exclusively with SW for almost two years now and would never go back. The only time I go back to VB6 (shudder) is when I test code in simple macros.
No - although I am seriously considering writing one. Other than the book out there by Mike Spens (which uses VB6), the only other good material is in the API help manual. Even that is pretty flimsy in my opinion. I gave it a shot for a while with SolidWorksDeveloper.com, but personal obligations have kept me off it for a good while now.