Exactly -- that will be your resonse to the client when the "new fantastic .NET solutions" needs fixes. When their product won't ship on time, because there are fixes that haven't been released. And then when the fixes break other things, as MS's fixes are known to do . . .
This cavalier attitude is *exactly* the kind of salesman that I think should be shunned industry-wide.
If you sell them a broken solution that needs fixing, like .NET, then it is *your* fault, *your* responsibility. Any money, time, effort they lose is because *you* misrepresented your product.
Are you telling them up front to expect product fixes? No. You're telling them it's ready for production.
Dude, that's fraud.
You mistook knowing that fixes will always be part of development with knowing there are problems to begin with. As a developer, you cannot possibly state that you code is perfect, only that you produce code without known problems. I do. Microsoft does, most of the time, and Sun does, most of the time. the business end is time to market. Of course, sloppy delivery will mean no support in the community.