My blog is a living documentation ;)

>how have you figured out what new features we have in the product?

I looked at the system class library and was at the PDC. I also have a very god ISV buddy at the ASP.Net team and one evangelist to talk to.

The feedback I got on my blog, it that your documentation are very poor, so I have been the extra living documentation and helped developers through my blog and also through the www.asp.net.

>We are working on getting a similar document out for Beta1.

Because there will be a lot of changes between the Beta 1 and Beta 2, wouldn't it be wise to wait to at least after the next CTP release?

I really like most of Whidbey... the table layout panel in winforms is by far the most critical feature to our company, believe it or not!!

I'm unhappy about the lack of 98/ME support, but with the addition of NTFS support and more modern features I can see why you guys made the decision.

There is a weird bug in the AppDomain.UnhandledException event - the event gets fired *after* .NET runs it's own unhandled exception dialog - effectively making the event useless. We desperately need it changed to execute *before* the .NET JIT stuff, so that we can provide our own "friendly error dialog". (http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=af9c628c-edac-45c5-89ac-72c7649e37c0)

The biggest, and easiest to implement feature I would like to see is new icons, believe it or not! Visual Studio has shipped with the same small, windows 3.1ish set of icons since the beginning of time. Microsoft also has *no* way to license their other icons, which puts many, many companies in a bad position.

We've actually had clients *require* (in their RFPs) that our software looks and feels like a Microsoft application! Take this for example - if I were to naughtily take the "chart" icon out of office, just about every user using our application would know exactially what it does. If I commission a third party to make one, the icon will be less familiar - especially if it isn't "inspired" by a microsoft icon.

The worst example of this I've ever seen was in Lotus Notes 5, where they had a "arrow going into cylinder" icon for save! Microsoft technically owns a copyright on the "disk" design!

I'd really like to see a large icon library for developers - it doesn't need to be things like application icons obviously, just those common things you need to make apps integrate nicely into windows without having it feel "foreign" to users.

Like I said, it's asking a lot, but at least some way to license them! :)

My biggest dislike auto-completion. Type the following into a c# source file while not looking at the editor:

int? i = null;

You will get:

int? if = null;

Argh! I hate editors that aren't WYSIWYT! It's like someone from the Office team managed to get auto-correct into the C# edtior.