拥抱asp.net 2.0时要小心 [英] Be careful about embracing asp.net 2.0
问题描述
嗨伙计，
我刚看了一个使用测试版完成的asp.net 2.0示例网站。
该网站是： http://www.ipona.com/samples/0321257278/default .aspx
当我尝试使用firefox浏览器运行网站时，它看起来很可怕。一半的UI东西搞砸了！我希望它是
，因为它只是一个测试版！
我们从开始就接受了asp.net。看看目前的b
浏览器市场，firefox正在获得越来越大的市场份额。所以，如果你在市场上发布一款产品，请不要认为你的用户只会在微软的IE下运行它（尽管ms会让你相信
几乎在所有情况下都会发生这种情况。）
如果发布的asp.net 2.0版本以相同的方式工作在交叉
浏览器，因为它现在有一个问题。
如果您认为您的
应用程序可能具有webforms，请小心拥抱asp.net 2.0在其他浏览器中运行。如果您在真正的
市场，请准备好您的应用程序在Internet Explorer中运行，
firefox，opera和safari。你不能要求unix或mac用户去运行你的软件。
我明白asp.net 2.0是一个很棒的软件。但是我不认为b $ b认为编写兼容的控件太难了，所以它在我上面提到的一些高级浏览器上优雅地运行
。例如，
现在可以使用动态html创建菜单控件，并且
支持所有高级浏览器。我希望微软的某个人正在阅读这个
的帖子。
我只需要这样说，如果微软的内部政策是
在开发基于Web的控件时支持IE，Web开发人员可能会选择其他框架，这些框架可以在多个
浏览器中正常工作。
或许是因为微软希望为第三方创造市场
控制!!!
评论？
SK
FWIW，ASP.NET团队已经表示他们正在努力支持任何
浏览器，它们发出的javascript（如验证控件，客户端脚本
回调等）。此外，您使用的任何ASP.NET控件都将符合XHTML标准
标记。
至于使用ASP.NET构建的任何特定网站，那么''仍然高达
网站的作者。因此，我可以轻松地建立一个网站，其中包含了一个很糟糕的网站。所以，请注意ASP.NET只是一个工具。
结果取决于你如何使用该工具。
-Brock
DevelopMentor
http://staff.develop.com/ballen
嗨伙计们，
我刚看了一个用测试版完成的asp.net 2.0示例网站。
网站是： http://www.ipona.com/samples/0321257278/default.aspx
当我尝试使用firefox浏览器运行网站时，它看起来很可怕。一半的UI东西搞砸了！我希望它是
因为它只是一个测试版！
自从它开始以来我们就接受了asp.net。看看目前的浏览器市场，firefox正在获得越来越大的市场份额。因此，如果您在市场上发布产品，请不要认为您的用户只会在Microsoft IE下运行它（即使ms会让您相信
这几乎会在所有情况下发生案例）。
如果发布的asp.net 2.0版本在交叉浏览器中的工作方式与现在相同，那么就会出现问题。
如果您认为您的应用程序可能必须在其他浏览器中运行，请小心为webforms包含asp.net 2.0。如果您在真正的市场，请准备好您的应用程序在Internet Explorer，火狐，歌剧和野生动物园中运行。你不能要求unix或mac用户去运行你的软件。
我知道asp.net 2.0是一个很棒的软件。但是我并不认为编写兼容的控件太难了，所以它在我上面提到的一些高级浏览器上优雅地运行。例如，现在可以使用动态html创建菜单控件，并且在所有高级浏览器中都支持
。我希望微软的某个人正在阅读这篇文章。
我只需要这样说，如果微软的内部政策是在开发基于网络的控件时支持IE， Web开发人员可能会选择其他框架，这些框架可以在多个浏览器中正常工作。
或许是因为微软希望为第三方控件创建市场！ !!
评论？
SK
Yay ..看起来像我成为了首先叫你一个巨魔。严重的是
虽然它已经处于测试阶段1 ......我很想知道你的
产品在发布前8个月的边缘有多粗糙！这个新闻组不是一个意见
页面，它是人们寻求帮助并讨论ASP.Net 1.x ...这是2.0
新闻组和2.0产品反馈网站，在那里抱怨。我只想要再说一遍，这就是好吧。没有什么可以评论其他
而不是... IT''IN BETA！
Karl
-
我的ASP.Net教程
http ：//www.openmymind.net/ - 新增和改进（是的，弹出窗口令人讨厌）
http://www.openmymind.net/faq.aspx - 非官方新闻组常见问题解答（更多内容
来了！）
" jojobar" < SK ****** @ yahoo.com>在消息中写道
news：11 ********************** @ g14g2000cwa.googlegr oups.com ...嗨伙计们，
我刚看了一个用测试版完成的asp.net 2.0示例网站。
网站是： http://www.ipona.com/samples/0321257278/default.aspx
当我尝试使用firefox浏览器运行网站时，它看起来很可怕。一半的UI东西搞砸了！我希望它是
因为它只是一个测试版！
自从它开始以来我们就接受了asp.net。看看目前的浏览器市场，firefox正在获得越来越大的市场份额。因此，如果您在市场上发布产品，请不要认为您的用户只会在Microsoft IE下运行它（即使ms会让您相信
这几乎会在所有情况下发生案例）。
如果发布的asp.net 2.0版本在交叉浏览器中的工作方式与现在相同，那么就会出现问题。
如果您认为您的应用程序可能必须在其他浏览器中运行，请小心为webforms包含asp.net 2.0。如果您在真正的市场，请准备好您的应用程序在Internet Explorer，火狐，歌剧和野生动物园中运行。你不能要求unix或mac用户去运行你的软件。
我知道asp.net 2.0是一个很棒的软件。但是我并不认为编写兼容的控件太难了，所以它在我上面提到的一些高级浏览器上优雅地运行。例如，现在可以使用动态html创建菜单控件，并且在所有高级浏览器中都支持。我希望微软的某个人正在阅读这篇帖子。
我只需要这样说，如果微软的内部政策是在开发基于网络的控件时支持IE， Web开发人员可能会选择其他框架，这些框架可以在多个浏览器中优雅地工作。
或许是因为微软希望为第三方控件创建市场！ !!
评论？
SK
考虑到添加任务非常简单/>
对任何ASP.NET应用程序的Firefox检测：
< case
match =" ^ Mozilla /（？''version ''（？''major''\ d +）（？''minor''\\\ +）（？''字母''\ w *））。*">
< case match =" ^ [5-9] \。"与= QUOT;
Hi Folks,
I just looked at a asp.net 2.0 sample site done with the beta version.
The site is: http://www.ipona.com/samples/0321257278/default.aspx
When I tried to run the site using the firefox browser, it looked
horrible. Half of the UI stuff just got screwed up! I hope it is
because it is just a beta!
We had embraced asp.net ever since it started. Look at the current
browser market, firefox is gaining increasing market share. So if you
release a product in the market, do not assume that your users will
only run it under microsoft IE (even though ms will make you believe
that this will happen in almost all the cases).
If the released version of asp.net 2.0 works in the same way in cross
browser as it does now then there is a concern.
Be careful about embracing asp.net 2.0 for webforms if you think your
application may have to run in other browsers. If you are in the real
market, be prepared for your application to run in internet explorer,
firefox, opera and safari. You cannot ask an unix or mac user to go get
a pc to run your software on ie.
I understand that asp.net 2.0 is a great software. However I do not
think it is too hard to write compatible controls so that it runs
gracefully on some advanced browsers I mentioned above. For example,
Menu controls can now be created using dynamic html and is supported in
all advanced browsers. I hope somebody from microsoft is reading this
post.
I just have to say this, if the internal policy in microsoft is to
favor IE while developing web-based controls, web developers will
probably select other frameworks that will work gracefully in multiple
browser.
Or maybe is it because microsoft wants to create market for third party
controls!!!
Comments?
SK
FWIW, the ASP.NET team has said that they are making efforts to support any
browser with the javascript they emit (like validation controls, client script
callbacks, etc). Also, any ASP.NET control you use will emit XHTML compliant
markup.
As for any particular website built with ASP.NET, well that''s still up to
the author of the website. So I could easily build a website that rocks in
FF and sucks in IE. So, just be aware that ASP.NET is simply a tool. The
result depends upon how you use the tool.
-Brock
DevelopMentor
http://staff.develop.com/ballen
Hi Folks,
I just looked at a asp.net 2.0 sample site done with the beta version.
The site is: http://www.ipona.com/samples/0321257278/default.aspx
When I tried to run the site using the firefox browser, it looked
horrible. Half of the UI stuff just got screwed up! I hope it is
because it is just a beta!
We had embraced asp.net ever since it started. Look at the current
browser market, firefox is gaining increasing market share. So if you
release a product in the market, do not assume that your users will
only run it under microsoft IE (even though ms will make you believe
that this will happen in almost all the cases).
If the released version of asp.net 2.0 works in the same way in cross
browser as it does now then there is a concern.
Be careful about embracing asp.net 2.0 for webforms if you think your
application may have to run in other browsers. If you are in the real
market, be prepared for your application to run in internet explorer,
firefox, opera and safari. You cannot ask an unix or mac user to go
get a pc to run your software on ie.
I understand that asp.net 2.0 is a great software. However I do not
think it is too hard to write compatible controls so that it runs
gracefully on some advanced browsers I mentioned above. For example,
Menu controls can now be created using dynamic html and is supported
in all advanced browsers. I hope somebody from microsoft is reading
this post.
I just have to say this, if the internal policy in microsoft is to
favor IE while developing web-based controls, web developers will
probably select other frameworks that will work gracefully in multiple
browser.
Or maybe is it because microsoft wants to create market for third
party controls!!!
Comments?
SK
Yay..looks like I get to be the first to call you a troll. Seriously
though, it''s in beta 1....I''d love to see how rough around the edges your
products are 8 months prior to release! This newsgroup isn''t an opinion
page, it''s for people to ask help and discuss ASP.Net 1.x...there''s a 2.0
newsgroup AND a 2.0 product feedback site, go complain there. I just want
to say it again, IT''S IN BETA. There''s nothing to comment on other
than...IT''s IN BETA!
Karl
--
MY ASP.Net tutorials
http://www.openmymind.net/ - New and Improved (yes, the popup is annoying)
http://www.openmymind.net/faq.aspx - unofficial newsgroup FAQ (more to
come!)
"jojobar" <sk******@yahoo.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...Hi Folks,
I just looked at a asp.net 2.0 sample site done with the beta version.
The site is: http://www.ipona.com/samples/0321257278/default.aspx
When I tried to run the site using the firefox browser, it looked
horrible. Half of the UI stuff just got screwed up! I hope it is
because it is just a beta!
We had embraced asp.net ever since it started. Look at the current
browser market, firefox is gaining increasing market share. So if you
release a product in the market, do not assume that your users will
only run it under microsoft IE (even though ms will make you believe
that this will happen in almost all the cases).
If the released version of asp.net 2.0 works in the same way in cross
browser as it does now then there is a concern.
Be careful about embracing asp.net 2.0 for webforms if you think your
application may have to run in other browsers. If you are in the real
market, be prepared for your application to run in internet explorer,
firefox, opera and safari. You cannot ask an unix or mac user to go get
a pc to run your software on ie.
I understand that asp.net 2.0 is a great software. However I do not
think it is too hard to write compatible controls so that it runs
gracefully on some advanced browsers I mentioned above. For example,
Menu controls can now be created using dynamic html and is supported in
all advanced browsers. I hope somebody from microsoft is reading this
post.
I just have to say this, if the internal policy in microsoft is to
favor IE while developing web-based controls, web developers will
probably select other frameworks that will work gracefully in multiple
browser.
Or maybe is it because microsoft wants to create market for third party
controls!!!
Comments?
SK
Considering that it''s quite a simple task to add
Firefox detection to any ASP.NET application :
<case
match="^Mozilla/(?''version''(?''major''\d+)(?''minor''\.\d+)(?''letters'' \w*)).*">
<case match="^[5-9]\." with="
这篇关于拥抱asp.net 2.0时要小心的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
