creating a process

  • Thread starter Thread starter Marco Martin
  • Start date Start date
M

Marco Martin

Good Morning Group,

I've created an app that "runs in the background "(the window state is
minimized, the showintaskbar is false, and it displays a notify Icon.).
This program will be running on a server and will be doing scheduled
maintenance on a database. What I'm wondering is, would this be better as a
process instead of an app? Since it will be running on a server and writing
to a log file, permissions could be an issue. I was told that a process
would be better suited. I've never coded for a "process" before. Is there
anything special I should know about creating a process? Would there be
major changes to my code if I pasted it inside a "Windows Project"?

Thanks and best regards,

Marco
 
Maybe they meant "Service"? Like web servers can run as a service. You
want to create a service?
 
Marco,
Functionality such as you describe is best wrapped up into a .NET Windows
Service. The Framework SDK and Visual Studio.NET help collection have
excellent examples of how to code these.
While debugging can be a little more difficult than a Winforms app running
as a NotifyIcon, it's generally well worth the extra effort to learn how to
do it.
VS.NET has a special project type, "Windows Service" that gives you all the
infrastructure to get started, all pre-written.
Peter
 
Yes, Service is what I meant. Thanks for the reply. I have a quick (newbie
type) question. Opening Task Manager, I can view Applications and
Processes. Some of the processes are actualy Apps. How does windows make
the difference? For example, svchost.exe is a process and not an app. ..

Marco
 
Back
Top