site requires that there is an "always running" condition.

Question

0.00/5 (No votes)

See more:

I'm creating a ASP.NET .NET 4.0 website and part of this site requires that there is an "always running" application. Normally I would create a Windows Service for this, but the site will be hosted within a shared hosting environment, and unless I get a virtual server, then this isn't a possibility.

My first thought was to have a thread running in the background that would do this and it would be created on Application_Start and destroyed on Application_End. I've looked around and this seems like it could be an option, but I would of course have to hit the site in order to cause the Application_Start to be called and if the associated AppPool is recylced, then this process would have to be repeated (so I believe?!?).

Within a normal ASP.NET website does these seem possible? I m developing an ASP.NET(with sql server) application.

Posted 7-Oct-13 2:09am

heresanjay01

Updated 7-Oct-13 2:16am

v2

Add a Solution

Comments

Mahesh Bailwal 7-Oct-13 10:01am

why you need "always running" application.?

heresanjay01 8-Oct-13 7:31am

i want sand mail delay process and i does't want sand if the mail send using background thread it is possible.

Mahesh Bailwal 8-Oct-13 9:28am

I think you can go ahead with this approach I don’t see any technical hurdle in that except that you need to hit web site to start the thread.

Although this design is not a recommended one and I believe you are also aware of that.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)