It would seem to me to be common sense that internal developers would spend more time on Winforms. And I've not talked to too many corporate developers at the gatherings I've attended.

So I feel comfortable spending time on Winforms development for that reason alone.

Consultants/Contractors I've talked to seem to be able to keep extremely busy on their asp.net projects, so they've not had a need to delve into winforms. I've heard that as a reason from several why they know little about winforms.

>I would think winforms are better also. But I've been asking around at events I've recently attended as well as reading up. People I've talked to at events are rarely, if ever, working on winforms projects. And it appears that 80% of job openings require asp.net.
>
>Hey, Perry,
>
>I've seen some of that as well. Many are actually not aware (or not fully aware) of what can be done with a smart-client, click-once model. I know some sharp ASP.NET developers who know (by their own admission) little about what can be done with winforms and web services.
>
>Also, I see less ads for Winform developers, because these are often built for internal applications by in-house developers (as opposed to consultants/contractors). Turnover rate for in-house developers is generally a little less often.
>
>Kevin