Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Performance / January 2005

Tip: Looking for answers? Try searching our database.

writing a "permanent" console application

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Amanda Pearls - 23 Jan 2005 11:22 GMT
Hello,
i need to write a simple console app which checks every 5 minutes or
so whether the website is available or not.

so after the start, it kind of runs till the windows is down...

how to do that, with threads?
what about perfomance issues? do i need to "kill" some of the objects?
any help is appreciated

thank you
Sherif ElMetainy - 23 Jan 2005 20:48 GMT
Why not just make it a console application that checks for the website then
dies, and add a scheduled task to windows to run it every 5 minutes?
> Hello,
> i need to write a simple console app which checks every 5 minutes or
[quoted text clipped - 7 lines]
>
> thank you
Alvin Bruney [MVP] - 23 Jan 2005 23:15 GMT
a windows service might be more appropriate for that type of application it
is needed to run constantly

Signature

Regards,
Alvin Bruney

> Why not just make it a console application that checks for the website
> then
[quoted text clipped - 10 lines]
>>
>> thank you
Sherif ElMetainy - 24 Jan 2005 23:07 GMT
A console application scheduled using windows task scheduler to run every 5
minutes is easier to implement and won't take take memory when it is not
running (which is actually most of the time)

> a windows service might be more appropriate for that type of application it
> is needed to run constantly
[quoted text clipped - 13 lines]
> >>
> >> thank you
Michael Pearson - 25 Jan 2005 22:41 GMT
...but if the machine is not logged in or gets rebooted, the tasks will not
execute.

The service is the way to go if this is more mission critical, the EXE +
scheduled task is it's not as critical.  Considering the requirements for
this project, I'd go service.

Michael

> A console application scheduled using windows task scheduler to run every 5
> minutes is easier to implement and won't take take memory when it is not
[quoted text clipped - 18 lines]
> > >>
> > >> thank you
Sherif ElMetainy - 27 Jan 2005 16:32 GMT
The Windows Task Scheduler Runs as a Service, executes the commands even if
no interactive user is logged on.

> ...but if the machine is not logged in or gets rebooted, the tasks will not
> execute.
[quoted text clipped - 29 lines]
> > > >>
> > > >> thank you

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.