Looking for ISP that can host a windows service

  • Thread starter Thread starter Johann Blake
  • Start date Start date
J

Johann Blake

I'm developing an application in C# that needs to run as a Windows service.
I'm looking for an Internet Service Provider (ISP) to host my application.
Since I'm on a shoe-string budget, I can only afford using a shared server
and not a dedicated one.

The problem is that most ISPs don't allow you to install your application as
a Windows service. Unfortunately, my application must run as a service
because it must always be up and running whenever the server is started. It
is an application that acts as a TCP server (TCPListener) listening to
incoming requests on a particular port. It cannot be started with an ASP.NET
page.

Has anyone come across an ISP who allows installing a Windows service
application without charging an arm or leg for doing it?

The other possibility is that I could write an ASP.NET page and call it
manually to install my TCP application as a Windows service. It would
involve writing to the registry and possibly storing some files on the
server but the ISP might be ticked off about me doing that and prevent it. I
personally don't see the problem with my code running as a Windows service
since my code can just as easily screw the system as ASP.NET code. Running
as a service simply adds the benefit of starting the application when the
server starts.

Thanks for any info.

Johann Blake

Mobile Solutions using Web Services
www.closerworlds.com/eng
 
Johann,

I seriously doubt that you are going to be able to do this. Having a
service running on a shared machine is just too much of a security risk.
Also, the fact that you are opening up a port is something that they
definitely don't want (and shouldn't allow either).

For something like this, you MUST get a dedicated server. If you think
of it, if you can place a service on a machine, then other people must be
able to, and you don't want THEIR services compromising you.

Hope this helps.
 
Nicholas,

There is absolutely not security difference when running my code as
ASP.NET "code-behind". I can just as easily screw the system from an
ASP.NET page if I really want to. As for opening a port, the only thing
preventing this would be a firewall.

Johann
 
Johann,

There is a security difference. ASP.NET by default runs under the
ASPNET local account. This account is not going to be able to open a socket
connection to connect to another machine.

By default, in a shared environment, I can't imagine that you are given
any permissions beyond what the ASPNET account would afford you.

Also, on a shared server, if you can run a service, then other people
can run services, and this is just too much of a risk. I can't imagine
anyone that would allow this who is at the same time concerned with
guaranteeing any kind of uptime to his customers.
 
Back
Top