I know that you can use WIA from .net ecosystem without (too) much hassle, but I've found using WIA this way, well, at least erratic. I've seen my code behave perfectly to not working at all to some WIA features not working and refusing to play at all, let alone nice.
You can read about it in my WIA 2.0 HP ScanJet 7650 specific problems question which didn't get a single comment, let alone answer in six months.
So, I'm willing to buy WIA .NET component that works, for a reasonable amount of money - reasonable being up to $300. I've been browsing aroung ComponentSorce and there are many $2000 brontosaurses that do TWAIN and eat small children if not treated nice, but not a single WIA .NET component.
Oh yeah, and a little rant - MSDN's documentation and examples on WIA are really really substandard.
UPDATE - To all who think that this problem can be solved with reading proof-of-concept and look-it-works articles with sample code on WIA - it cannot. To get from look-it-works to reliable scanning support for many devices is a lot of work. I've tested three different scanners on my computer using WIA from .net, and just when you think you've got some detail figured out, you plug in another scanner and see that you haven't figured out anything. That is why I'm willing to pay for this.