Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > ASP .Net Web Controls > A DotNet Severe Limitation ?

Reply
Thread Tools

A DotNet Severe Limitation ?

 
 
Dave Brown
Guest
Posts: n/a
 
      02-11-2004
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.


 
Reply With Quote
 
 
 
 
Cowboy \(Gregory A. Beamer\)
Guest
Posts: n/a
 
      02-11-2004
Limitation? Yes. Severe? How many people does it impact? I would venture
that while this is limiting, it is only severe to the few trying to do it
right now. In the future, the severity may change. If it is perceived as
large enough, MS will change it.

Most people pushing functionality that requires Windows Forms are not
embedding Windows Forms, like ActiveX, but actually deploying the WIndows
Forms apps. This is the direction MS is pushing with zero deployment.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Dave Brown" <dave.AT.dbws.net> wrote in message
news:uX$(E-Mail Removed)...
> 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.
>
>



 
Reply With Quote
 
 
 
 
Dave Brown
Guest
Posts: n/a
 
      02-11-2004
Isnt this method zero deployment ?
Having a complex control running from the browser should be the simplest for
people to use, all they need to do is have the framework installed then go
to the website hosting the control.

rgds

Dave


"Cowboy (Gregory A. Beamer)" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
> Limitation? Yes. Severe? How many people does it impact? I would venture
> that while this is limiting, it is only severe to the few trying to do it
> right now. In the future, the severity may change. If it is perceived as
> large enough, MS will change it.
>
> Most people pushing functionality that requires Windows Forms are not
> embedding Windows Forms, like ActiveX, but actually deploying the WIndows
> Forms apps. This is the direction MS is pushing with zero deployment.
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> ************************************************** ********************
> Think Outside the Box!
> ************************************************** ********************
> "Dave Brown" <dave.AT.dbws.net> wrote in message
> news:uX$(E-Mail Removed)...
> > 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.
> >
> >

>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Was security hole in dotnet 1.1 fixed in dotnet 2.0 Chuck ASP .Net 3 02-08-2007 05:31 PM
microsoft.public.dotnet.faqs,microsoft.public.dotnet.framework,microsoft.public.dotnet.framework.windowsforms,microsoft.public.dotnet.general,microsoft.public.dotnet.languages.vb Charles A. Lackman ASP .Net 1 12-08-2004 07:08 PM
A DotNet Severe Limitation ? Dave Brown ASP .Net 2 02-11-2004 02:07 PM
A DotNet Severe Limitation ? Dave Brown ASP .Net Building Controls 2 02-11-2004 02:07 PM
microsoft.public.dotnet.languages.vb,microsoft.public.windowsxp.print_fax,microsoft.public.dotnet.framework.aspnet SpamProof ASP .Net 0 10-21-2003 12:32 PM



Advertisments