Re: Dot Net Limitations
From: doug (anonymous_at_discussions.microsoft.com)
Date: 02/11/04
- Next message: Mark: "Re: Errors with setting up an asp.net site on host (IIS)"
- Previous message: Aaron Bertrand - MVP: "Re: ADO Constants"
- In reply to: Dave Brown: "Re: Dot Net Limitations"
- Next in thread: Dave Brown: "Re: Dot Net Limitations"
- Reply: Dave Brown: "Re: Dot Net Limitations"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 11 Feb 2004 06:20:00 -0800
Dave,
I read that from the previous post. It doesn't help
much...
1: What is the url you are using when using a different
port?
2: What version of IIS?
3: What does happen?
4: What are the exact errors you see in IE and in the
event viewer? Turn off friendly error messages in your
browser first.
doug
>-----Original Message-----
>Hi Doug,
>
>I have used the SimpleControl.dll that comes with
the .net sdk.
>Basically I created a html page in notepad that has an
object tag calling
>the
>simplecontol.dll.
>Then I copied both the dll and the html file into a new
virtual directory
>that has Scripts Only permissions.
>Then I call the page and the control appears fine.
>BUT only when IIS is running port 80, When I change to
say 90 for example
>the control is not shown.
>
>This is the Object tag I use...
><object id="simpleControl1"
>
>classid="SimpleControl.dll#Microsoft.Samples.WinForms.Cs.
SimpleControl.Simpl
>eControl"
> height="300"
> width="300">
> <param name="Text" value="Simple Control">
></object>
>
>Even if I put a fully qualified URL to the control when
i change port,
>adding the :90 to the domain name it doesnt work. I
think its osmething
>additional that has to be configured on the server
somehow.
>
>Rgds,
>
>Dave.
>
>"doug" <anonymous@discussions.microsoft.com> wrote in
message
>news:eabd01c3f0a6$cfee1570$a501280a@phx.gbl...
>> You should really keep your posts to one thread. Also,
>> answer my questions (from your previous post) with
>> specific answers and we maybe able to help. Saying
>> something will not display or will not work is that
same
>> as going to the doctor and saying I have a pain. Please
>> fix it Doctor.
>>
>> doug
>> >-----Original Message-----
>> >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.
>> >
>> >
>> >.
>> >
>
>
>.
>
- Next message: Mark: "Re: Errors with setting up an asp.net site on host (IIS)"
- Previous message: Aaron Bertrand - MVP: "Re: ADO Constants"
- In reply to: Dave Brown: "Re: Dot Net Limitations"
- Next in thread: Dave Brown: "Re: Dot Net Limitations"
- Reply: Dave Brown: "Re: Dot Net Limitations"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|