ASP.Net debate

Replying to my last post Jorge replied:

Excellent post, Phil.

I think that the strongly-typed aspect of .NET is one example of the double-edged sword. It gives you better performance and better compile-time checking, but the cost is that tackling a problem that was quick in, say, JScript, is often much more complicated (more lines of code, more types to deal with, etc).

Even though I like .NET, I often find myself working in old ASP/JScript when I need to through something together quickly.

For building a production-quality web app, however, I'd go with ASP.NET (and my own custom controls) in a heartbeat.

Jorge, I can't be more agree to that (including that you liked my post ;-)) ! On the Javascript front, you have to deal with more than expected, like for example where you register your script, at the start of the page, or at the end. That's not the same if you create your controls dynamically.
But, be aware I just want to help by contributing to this debate, not to demolish ASP.Net. On the contrary !
Because I was so delighted but what I could achieve in terms of complexity with .Net, som stuff that I would never imagine doing with ASP.
No it's just I heard this ASP.Net 2.0 is on the tracks, and I hope that Microsoft will not listen only the MVPs, but as they did for the first version, all the community.