点网限制 [英] Dot Net Limitations

查看:71
本文介绍了点网限制的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我相信我已经发现DotNet的严重限制,相对于在WebPages中托管Windows窗体控件的



看来这只有当网络是在端口80上配置。任何

其他端口和控件都不会显示。

经过几天搜索新闻组/各种论坛后我有

发现其他帖子要求提供有关此异常的信息,但是没有人有

找到了解决方案。

Microsoft正在做什么?在

备用端口上运行似乎是常见的情况,被限制为默认的80似乎很荒谬。


Dave。

I believe I have found a severe limitation of DotNet, with respect to
hosting Windows Form Controls in WebPages.
It appears this is only possible when the web is configured on Port 80. Any
other port and the control will not display.
After a couple of days of searching the newsgroups/various forums I have
found other postings requesting information on this anomaly yet nobody has
found a solution.
What are Microsoft doing with this ? It seems a common situation to run on
alternate ports, being restricted to the default 80 seems ludicrous.

Dave.

推荐答案

希望您确实知道它们被称为Windows窗体控件,而不是更高级的Web窗体控件。你正在做一些微软不支持*正式*的事情。如果真的没有解决方案,运气不好,那从来就没有意义上的工作。

----- Dave Brown写道:-----


我相信我发现了DotNet的严重限制,相对于在WebPages中托管Windows窗体控件的



看来这只是可能的在端口80上配置W​​eb时。任何

其他端口和控件都不会显示。

经过几天搜索新闻组/各种论坛后我

发现其他帖子要求提供有关此异常的信息,但是没有人有

找到了解决方案。

Microsoft正在做什么?在

备用端口上运行似乎是一种常见的情况,被限制为默认的80似乎很荒谬。


戴夫。

hope you do realize that there is a reason why they are called windows form controls, not fancier web form controls. you are doing something that''s not *officially* supported by Microsoft. If there''s truly no solution, tough luck, it was never meant to work in the first place.
----- Dave Brown wrote: -----

I believe I have found a severe limitation of DotNet, with respect to
hosting Windows Form Controls in WebPages.
It appears this is only possible when the web is configured on Port 80. Any
other port and the control will not display.
After a couple of days of searching the newsgroups/various forums I have
found other postings requesting information on this anomaly yet nobody has
found a solution.
What are Microsoft doing with this ? It seems a common situation to run on
alternate ports, being restricted to the default 80 seems ludicrous.

Dave.


当我将它设置为脚本和可执行文件时,它肯定是不行的..


即使在端口80上运行,它也有设置为仅脚本。当

否则控制权不会显示。

Dave Brown < dave.AT.dbws.net>在留言中写道

news:ev ************** @ TK2MSFTNGP09.phx.gbl ...
Hi when I set it to Scripts and Executables, its definately a no-go..

Even when running on port 80, it has to be set to Scripts Only. When
otherwise the control wont show.
"Dave Brown" <dave.AT.dbws.net> wrote in message
news:ev**************@TK2MSFTNGP09.phx.gbl...
我相信我找到了严格限制DotNet,关于在WebPages中托管Windows窗体控件。
看起来这只有在端口80上配置W​​eb时才有可能。
任何其他端口和控件将不显示。
经过几天搜索新闻组/各种论坛后,我发现其他帖子要求提供有关此异常的信息,但没有人找到解决方案。
什么是微软这样做?在
备用端口上运行似乎是一种常见的情况,限制为默认的80似乎很荒谬。

戴夫。
I believe I have found a severe limitation of DotNet, with respect to
hosting Windows Form Controls in WebPages.
It appears this is only possible when the web is configured on Port 80. Any other port and the control will not display.
After a couple of days of searching the newsgroups/various forums I have
found other postings requesting information on this anomaly yet nobody has
found a solution.
What are Microsoft doing with this ? It seems a common situation to run on
alternate ports, being restricted to the default 80 seems ludicrous.

Dave.



实际上,在Internet Explorer中托管WinForms控件不仅支持
,而且还受到Microsoft的鼓励。

Daniel Jin <一个******* @ discussions.microsoft.com>在留言中写道

news:13 ********************************** @ microsof t.com ...
Actually, hosting WinForms controls in Internet Explorer is not only
supported but encouraged by Microsoft.
"Daniel Jin" <an*******@discussions.microsoft.com> wrote in message
news:13**********************************@microsof t.com...
希望你确实知道它们被称为windows
表单控件,而不是更高级的Web表单控件。你正在做一些事情

微软不支持*正式*。如果真的没有

的解决方案,那么运气不好,首先就没有意义。

----- Dave Brown写道: - ---

我相信我已经发现了DotNet的严重限制,关于在WebPages中托管Windows窗体控件。
看起来这只有在网络是在端口
80上配置。任何其他端口和控件都不会显示。
在搜索新闻组/各种论坛几天后,我发现其他帖子要求提供有关此异常的信息
没人找到解决方案。
微软在做什么呢?似乎常见的情况是
在备用端口上运行,被限制为默认的80似乎很荒谬。

Dave。
hope you do realize that there is a reason why they are called windows form controls, not fancier web form controls. you are doing something
that''s not *officially* supported by Microsoft. If there''s truly no
solution, tough luck, it was never meant to work in the first place.

----- Dave Brown wrote: -----

I believe I have found a severe limitation of DotNet, with respect to
hosting Windows Form Controls in WebPages.
It appears this is only possible when the web is configured on Port 80. Any other port and the control will not display.
After a couple of days of searching the newsgroups/various forums I have found other postings requesting information on this anomaly yet nobody has found a solution.
What are Microsoft doing with this ? It seems a common situation to run on alternate ports, being restricted to the default 80 seems ludicrous.

Dave.



这篇关于点网限制的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆