Office - the best of times and the worst of times

Every 3 or 4 months I'm enticed back into Office development; lured back by some incredibly interesting collaboration tools.  And it seems that every time I'm left thinking that someone in the Office camp really just doesn't understand me.

Here's some tips that I have for the Office team:

1. People like me are lazy dorks.  Make it easier to create assembly based smart tags.  Here's what I want.  A manifest file which points to a .dll in the same dir. which references a Recognizer class and an Action class.
2. Don't ship the hardest demo that you can think of as your tute.  The demo that you shipped with IBF really didn't need Sharepoint and Reporting Services in there now… did it?  It probably didn't even need all 3 of those web services.  If you want me to use it, I have to be able to believe that I can do something trivial but cool in an afternoon.
3. If you are going to ship something like the .NET integration with InfoPath, call it a beta until you get it right… that way I'll feel privileged to use it and not curse you for all the little hacks that I have to work around.
4. Don't make Server 2003 a dependancy for getting a demo up and running.

That's all for now; just 3 4 little things to help you understand your customers a little bit better.

[Edit: added the gripe about Server 2003 dependencies]