VS.NET IDE is very intuitive. There are some glitches but with as robust as it is, MS would have been hard pressed not to screw up somewhere. There is no IDE as comprehensive. You COULD use #develop for learning purposes, but as stated above, not for anything on a schedule.
Consider that #develop is in an open source alpha/beta stage and will UE on you. The #develop team has implemented some things that are definitely missing from VS.NET ide like a few code completion macros:
prop int counter (hit Alt+Q here)
turns into:
private int counter;
public int Counter
{
get
{
return this.counter;
}
set
{
this.counter=value;
}
}
It's a nice feature to have, but can easily be duplicated in minutes from within the VS.NET Macros IDE (and it runs a lot faster too).
I think that #develop is an awesome idea, and once it has been extensively bug tested and developed, that it may give the community at large a viable alternative to using a Microsoft product. However, with VS.NET 2005 about to break, #develop may be a little to little a little too late.
Seth Webster