You could use notepad and the.NET framework SDK no problem. And I would give VS.NET 2003 a shot. It's only like twenty bucks if you own VS.NET 2002, and it performs much better.
That being said, I've been working with VS.NET 2002 since beta 2 and have never seen it throw an exception at me. I'm going to go out on a limb and say you've got some faulty hardware or you've hosed your IIS settings (very easy to do).
And I can't believe you mention hating a crappy IDE, and loving Java in the same breath. Java has had the worst collection of IDEs EVER. Notepad and command line was the only way to be productive.
I am a geek training other geeks I guess. I do not teach proprietary software or anything like that, mostly just training on products like Visual Basic and SQL Server. People come to me to do the training, I very rarely get sent to a company to do training (cheaper for companies to send people to us). If this is the route you are going, I would look into these things
1) Talk to the instructor. After the economy went into the pooper, most companies didn't keep the smart trainers, they kept the people who were ok at lots of stuff. You'll see a lot of MCSE, MCDBA, CCIE, MCSDs out there claiming to be able to teach anything. They can't. Make sure your trainer has a passion for what they are teaching.
2) Try to find out if there will be "career changers" in the classes. A class full of career changers (former truck drivers who heard you can make 85,000 a year being an MCSE an other missinformed individuals) goes entirely different than one with people who need to know this to do their job, or are looking to better themselves. Each class with people who really use this stuff is much more enjoyable and enlightening because you see all kinds of view points and questions. Good times
3) Make sure you read the outlines. I taught a class on the Programming the.NET Framework. The outline clearly shows that we will be covering topics like streams, serialization, threading, remoting, memory management. Kinda the nitty grittys. Well, I get someone in my class who right away asks when we'll get to webpages. Um, who signs up for a 5 day class without reading the outline for the class? I teach 10 seperate.NET courses, 5 different VB6 courses and three seperate SQL Server courses. There is a lot of variety out there...
4) Keep an open mind. Ask questions about the how and why. Your instructor might not have even thought of your question yet, but if they are anything like me they'll help you figure it out.
Slashdot Mirror
You could use notepad and the .NET framework SDK no problem. And I would give VS.NET 2003 a shot. It's only like twenty bucks if you own VS.NET 2002, and it performs much better.
That being said, I've been working with VS.NET 2002 since beta 2 and have never seen it throw an exception at me. I'm going to go out on a limb and say you've got some faulty hardware or you've hosed your IIS settings (very easy to do).
And I can't believe you mention hating a crappy IDE, and loving Java in the same breath. Java has had the worst collection of IDEs EVER. Notepad and command line was the only way to be productive.
I am a geek training other geeks I guess. I do not teach proprietary software or anything like that, mostly just training on products like Visual Basic and SQL Server. People come to me to do the training, I very rarely get sent to a company to do training (cheaper for companies to send people to us). If this is the route you are going, I would look into these things 1) Talk to the instructor. After the economy went into the pooper, most companies didn't keep the smart trainers, they kept the people who were ok at lots of stuff. You'll see a lot of MCSE, MCDBA, CCIE, MCSDs out there claiming to be able to teach anything. They can't. Make sure your trainer has a passion for what they are teaching. 2) Try to find out if there will be "career changers" in the classes. A class full of career changers (former truck drivers who heard you can make 85,000 a year being an MCSE an other missinformed individuals) goes entirely different than one with people who need to know this to do their job, or are looking to better themselves. Each class with people who really use this stuff is much more enjoyable and enlightening because you see all kinds of view points and questions. Good times 3) Make sure you read the outlines. I taught a class on the Programming the .NET Framework. The outline clearly shows that we will be covering topics like streams, serialization, threading, remoting, memory management. Kinda the nitty grittys. Well, I get someone in my class who right away asks when we'll get to webpages. Um, who signs up for a 5 day class without reading the outline for the class? I teach 10 seperate .NET courses, 5 different VB6 courses and three seperate SQL Server courses. There is a lot of variety out there...
4) Keep an open mind. Ask questions about the how and why. Your instructor might not have even thought of your question yet, but if they are anything like me they'll help you figure it out.