OptionExplicit

[CMM]

I just realized that strict type checking does't seem to work in ASP.NET 2.0
no matter what I do (I set "strict" in Web.Config, I set it on the WebForm
level.... what, do I have to put it at the top of every code module a ala
VB3.0??? Am I missing something here?

I know I've been griping about VS2005 for some time (in past posts) but this
just takes the cake!
I can now say with 100% certainty that the ASP.NET 2.0 Team is on drugs. Are
the entry level programmers at MS sent to the ASP.NET team??? Do they have a
Team Lead? There are just soooooo many things that are simply head-smacking
"what were they thinking?" things in ASP.NET 2.0.

More Info:
http://lab.msdn.microsoft.com/produ...edbackid=3c1c9898-8076-4f69-a5e2-e99573d03c6e

 

[CMM]

I meant to title the post OptionStrict.

 

[Teemu Keiski]

I asked ScottGu about this a while ago, and they are pushing this to the
..NET Framework 2.0's next SP.

 

[CMM]

IMHO, ScottGu- and most of the rest of the team- need to be fired. ASP.NET
1.0 and 1.1 were *undersdantably* rough around the edges. But, there is just
no justification for ASP.NET 2.0 being as hafl-assed as it is. Sure, the
underlying technology is cool (though nothing "new" considering J2EE), but
it is painfully obvious that the ASP.NET Team has no idea how people how
people undertake web site creation or maintannence.

Sadly (and I hate say it). but FrontPage is an EONs better web designer that
any of the designers in .NET. Sure, VS2005 it's "code warrior" oriented, but
that doesn't mean it's WYSIWIG Editor has to be WORSE than FP Express circa
1998.

Just what the hell were they working on
for the past 3 years? The much-maligned new "project model?" The
not-much-better-than-UserControl MasterPages? or the not-for the-timid
no-"Visual Designer"-having CompositeControl?

The retarded Localization "features" where the "Expressions
Editor" doesn't even recognize Global resources, and the brain-dead CssClass
property that, in the Property Editor, has no knowledge of existing rules in
the already associated StyleSheet?????

What exactly have they been working on fot the last three years? The
"adaptive rendering" that can't even recognize browsers that support
JavaScript, but (for whatever reason) have it disabled?

ASP.NET 2.0 is cool... But then again so was 1.1.
2.0 is just a sad joke.


--
-C. Moya
www.cmoya.com

I asked ScottGu about this a while ago, and they are pushing this to the
.NET Framework 2.0's next SP.

 

[Teemu Keiski]

You know what. I directed this msg to ASP.NET Team, and ScottGu himself
checked this one. So he is aware of your opinions...

Response was.
"
The project structure change ended up being more painful than we expected --
that was obviously a goof on our part (not that we introduced the new
project model, which we've actually seen a lot of people like, but rather
that we didn't support *both* the new one and the WAP one the day we shipped
VS 2005). That is why we've been working hard to make the WAP one available
as a web-download and to integrate it into VS 2005 SP1.
The WAP option (http://webproject.scottgu.com/) would fix his original
question around option explicit

"

--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke

IMHO, ScottGu- and most of the rest of the team- need to be fired. ASP.NET
1.0 and 1.1 were *undersdantably* rough around the edges. But, there is
just no justification for ASP.NET 2.0 being as hafl-assed as it is. Sure,
the underlying technology is cool (though nothing "new" considering J2EE),
but it is painfully obvious that the ASP.NET Team has no idea how people
how people undertake web site creation or maintannence.

Sadly (and I hate say it). but FrontPage is an EONs better web designer
that any of the designers in .NET. Sure, VS2005 it's "code warrior"
oriented, but that doesn't mean it's WYSIWIG Editor has to be WORSE than
FP Express circa 1998.

Just what the hell were they working on
for the past 3 years? The much-maligned new "project model?" The
not-much-better-than-UserControl MasterPages? or the not-for the-timid
no-"Visual Designer"-having CompositeControl?

The retarded Localization "features" where the "Expressions
Editor" doesn't even recognize Global resources, and the brain-dead
CssClass
property that, in the Property Editor, has no knowledge of existing rules
in
the already associated StyleSheet?????

What exactly have they been working on fot the last three years? The
"adaptive rendering" that can't even recognize browsers that support
JavaScript, but (for whatever reason) have it disabled?

ASP.NET 2.0 is cool... But then again so was 1.1.
2.0 is just a sad joke.

 

[Ken Halter]

Just what the hell were they working on
for the past 3 years?

Marketting ;-)