port 80

[Alexandre Brisebois]

Hi all,

How can I have my application running on port 80 while ISS and other
applications also run through port 80?
for remoting (without hosting it in IIS) and or simply using sockets.
regards,
Alexandre Brisebois

[Ignacio Machin \( .NET/ C# MVP \)]

Hi ,

You cannot, only one app can be listening in a port.

Why not use another port?
--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"Alexandre Brisebois" <al*****************@gmail.com> wrote in message
news:11**********************@i40g2000cwc.googlegr oups.com...

Hi all,

How can I have my application running on port 80 while ISS and other
applications also run through port 80?
for remoting (without hosting it in IIS) and or simply using sockets.
regards,
Alexandre Brisebois

[Nicholas Paldino [.NET/C# MVP]]

Alexandre,

You can't. Only one app at a time can bind to a socket. If port 80 is
already taken by IIS, then you don't have much of a choice, you have to pick
a different socket.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Alexandre Brisebois" <al*****************@gmail.com> wrote in message
news:11**********************@i40g2000cwc.googlegr oups.com...

Hi all,

How can I have my application running on port 80 while ISS and other
applications also run through port 80?
for remoting (without hosting it in IIS) and or simply using sockets.
regards,
Alexandre Brisebois

[Peter Bromberg [C# MVP]]

Alexandre,
That's a tricky question, because if you run a remoting app hosted in IIS it
isn't a problem at all - it acts (and actually is) just like any other IIS
application.

However, if you have a custom app that is attempting to talk on port 80 of
the same IPAddress that IIS is listening on, then yes, it will fail.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Alexandre Brisebois" wrote:

Hi all,

How can I have my application running on port 80 while ISS and other
applications also run through port 80?
for remoting (without hosting it in IIS) and or simply using sockets.
regards,
Alexandre Brisebois

[William Stacey [MVP]]

Use a different IP address then what IIS is listening on (if IIS is
listening on all IPs, then change that).

--
William Stacey [MVP]

"Alexandre Brisebois" <al*****************@gmail.com> wrote in message
news:11**********************@i40g2000cwc.googlegr oups.com...
| Hi all,
|
| How can I have my application running on port 80 while ISS and other
| applications also run through port 80?
| for remoting (without hosting it in IIS) and or simply using sockets.
|
|
| regards,
| Alexandre Brisebois
|

[Flowering Weeds]

"Alexandre Brisebois"

How can I have my application running on
port 80 while ISS and other applications also
run through port 80?
for remoting (without hosting it in IIS) and or
simply using sockets.

With Vista's IIS7 (in versions Home Premium
and up) and with Vista's Http.sys 2.0 (in all
versions) this is very easy to do! Just use the
System.Net.HttpListener class!

Now some Vista Beta testers should test all
the above and let us know if Microsoft did fix
this IIS 5.1 and IIS6 bug in IIS7 and Http.sys
2.0 (Home versions are out too) before the
beta tests are over with in Vista!

Http.sys 2.0 in Vista is like a full web sever
in itself - where as Http.sys 1.0 (Windows
XP SP2 and Windows 2003) is more like a
mini web server!

Not sure - but does the new .NET 3.0 objects
install http.sys 2.0 on Windows XP? Testers?

But even right now, with just Windows XP SP2
Home edition (and higher) and with .NET 2.0 a
user can access many different Windows
processes using the same http.sys 1.0 port!
But not with non http.sys aware programs like
the web servers IIS5.1 or Apache!

Say even Windows PowerShell (the new .Net
command line shell) can access Http.sys
(even on Windows XP SP2 Home Edition):

PS C:\Test1> get-wmiobject win32_operatingsystem |
select-object Caption, CSDVersion

Caption CSDVersion
------- ----------
Microsoft Windows XP Home Edition Service Pack 2

PS C:\Test1> [System.Net.HttpListener]::IsSupported
True

PS C:\> $listener = new-object System.Net.HttpListener
PS C:\> $listener.GetType()

IsPublic IsSerial Name BaseType
-------- -------- ---- --------
True False HttpListener
System.Object

So if you are using Windows for modern
HTTP / HTTPS usage, then learn how to
use the Windows Http.sys object!

[Peter Bromberg [C# MVP]]

Flowering,
The poor bloke is just trying to figure out how to run a remoting app
outside of IIS and whether he can still use Port 80!
Too many flowering weeds methinks.
:-)
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Flowering Weeds" wrote:

"Alexandre Brisebois"

How can I have my application running on
port 80 while ISS and other applications also
run through port 80?
for remoting (without hosting it in IIS) and or
simply using sockets.

With Vista's IIS7 (in versions Home Premium
and up) and with Vista's Http.sys 2.0 (in all
versions) this is very easy to do! Just use the
System.Net.HttpListener class!

Now some Vista Beta testers should test all
the above and let us know if Microsoft did fix
this IIS 5.1 and IIS6 bug in IIS7 and Http.sys
2.0 (Home versions are out too) before the
beta tests are over with in Vista!

Http.sys 2.0 in Vista is like a full web sever
in itself - where as Http.sys 1.0 (Windows
XP SP2 and Windows 2003) is more like a
mini web server!

Not sure - but does the new .NET 3.0 objects
install http.sys 2.0 on Windows XP? Testers?

But even right now, with just Windows XP SP2
Home edition (and higher) and with .NET 2.0 a
user can access many different Windows
processes using the same http.sys 1.0 port!
But not with non http.sys aware programs like
the web servers IIS5.1 or Apache!

Say even Windows PowerShell (the new .Net
command line shell) can access Http.sys
(even on Windows XP SP2 Home Edition):

PS C:\Test1> get-wmiobject win32_operatingsystem |
select-object Caption, CSDVersion

Caption CSDVersion
------- ----------
Microsoft Windows XP Home Edition Service Pack 2

PS C:\Test1> [System.Net.HttpListener]::IsSupported
True

PS C:\> $listener = new-object System.Net.HttpListener
PS C:\> $listener.GetType()

IsPublic IsSerial Name BaseType
-------- -------- ---- --------
True False HttpListener
System.Object

So if you are using Windows for modern
HTTP / HTTPS usage, then learn how to
use the Windows Http.sys object!

[Flowering Weeds]

"Peter Bromberg [C# MVP]"

The poor bloke is just trying to figure
out how to run a remoting app outside
of IIS and whether he can still use Port 80!

And now he has a lead on how to maybe
do it via Http.sys (and with or without IIS7)
too!

The days of "only" one process on one
port for Windows users are gone! Don't
live in the past programmers! Plant a new
flower! :)

[Alexandre Brisebois]

I greatly apreciate all your inputs on this question of mine,
I have read a lot, and always thought it was impossible, but it is nice
to see people thinking outside the normal closed box of the past, I
will have a look at Http.sys,

if you have any good resouces I would greatly apreciate it.

best regards,
Alexandre Brisebois

Flowering Weeds wrote:

"Peter Bromberg [C# MVP]"

The poor bloke is just trying to figure
out how to run a remoting app outside
of IIS and whether he can still use Port 80!

And now he has a lead on how to maybe
do it via Http.sys (and with or without IIS7)
too!

The days of "only" one process on one
port for Windows users are gone! Don't
live in the past programmers! Plant a new
flower! :)

[Flowering Weeds]

"Alexandre Brisebois"

I will have a look at Http.sys,
if you have any good resouces

For tons of links:

Windows Live Search
http://www.live.com/?q=http.sys+HTTP

And to "talk" to the programmers
who wrote http.sys:

Windows Network Development platforms,
technologies and APIs such as Winsock,
WSK, WinINet, Http.sys, WinHttp, QoS
and System.Net

Windows Network Development
http://blogs.msdn.com/wndp/

..NET Framework Networking and Communication
http://forums.microsoft.com/msdn/sho...id=40&siteid=1

Enjoy HTTP / HTTPS usage
with many processes,
on the same IP:Port,
at the same time,
via modern Windows methods! :)