WinForms VS. WebForms?

[Kasracer]

Yes, web development has allways been like this. However its not un-workable.

Obviously it's not un-workable but the fact of the matter is that it extends development and design time. We've obviously gotten around all of these areas but that doesn't mean WebForms take less time; they don't.

The problems your company seem to have encountered based on your post are training/skills issues not to do with the technology.

For your company your team doesnt seem to have the correct skillset to develop web apps. So a webform would be correct.

Wow.. that's incredibly rude (that or you're just ignoring my points, contorting them to fit your idea, and responding like I'm some sort of half-wit). I didn't realize you actually knew who everyone was, what their still sets are, etc. Also, you keep saying WebForm everytime you mean WebForm or WinForm; stop that.

So, explain to me how we lack appropriate training just because we've had some ViewState bloat (almost every commercial ASP.Net application I see has quite a bit; seems like no one cares to clean it up like we did). Or because we found out that handling row commands in a GridView in server controls (remember, server controls are not user controls) is a PITA (I should really say I found out; this was one of my items). Also, what does training have to do with useless ASP.Net events or general browser slowness with executing JavaScript?

I never said we were not capable of doing any of these things nor did I say we couldn't do them or we had difficulty doing them. Regardless of whether you're the king of ASP.Net or not, these things take extra development time that WinForms do not need to account for.

You seem to be confusing what exactly we're talking about. WinForms take less time to develop due to many less steps you have to take. This does not mean that ASP.Net is too hard or anything remotely like that.