Window service equivalent for onhandlecreated & wndproc functions (from C#)

Question

1.00/5 (1 vote)

See more:

Is there any equivalent for OnHandleCreated & WndProc functions for a Window Service similar to the one in C# for a form?

I need to implement WatchBP SDK(USB Library) for window Service that works with WebSocket to get data from the device to Web UI.

in SDK below methods need to implement but these methods not getting called in Window Service so notification not received from Device to window service.

protected override void OnHandleCreated(EventArgs e)
    {
        base.OnHandleCreated(e);
        this.watchBPOfficeHid.RegisterHandle(this.Handle);
        
    }
    protected override void WndProc(ref Message m)
    {
        base.WndProc(ref m);
        this.watchBPOfficeHid.ParseMessages(ref m);
    }

although I inherit Window service class from System.Windows.Forms.Form but above method not getting called.

In WinForms we could use OnHandleCreated to get the handle as soon as it is created. Is it any alternative for this in window service?

Any help would be appreciated.
Thanks in advance.

What I have tried:

Is there any equivalent for OnHandleCreated & WndProc functions for a Window Service similar to the one in C# for a form?

Posted 3-Aug-20 21:23pm

avnish kumar maddheshiya

Updated 4-Aug-20 5:35am

Add a Solution

3 solutions

Add a Solution

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)

OriginalGriff · Answer 1 · 2020-08-03T21:37:00

No. Services do not - and cannot - have a UI at all, cannot interact with the user, and do not respond to messages other than System messages. They do not have a Window Handle because ... they don't have a Window.

They can't be derived successfully from Form at all as a result.

You can't "work around" that - services are designed specifically to not have any UI components at all!

Garth J Lancaster · Answer 2 · 2020-08-03T23:44:00

While you could in theory write a C# service that uses P/Invoke to do this (manage a hidden window), I doubt the effort required would weigh up against the one-use value of that approach.

I think you are far better off sticking to a Winforms (or WPF) application, and daemonising it (making it robust, restartable, able to minimise/hide) as much as you can and/or having a 'watchdog' process for it - in fact, if you start it through the Windows Task Scheduler, you may be able to specify the parameters to 'keep it alive', else write a watchdog service to monitor/restart your app

honey the codewitch · Answer 3 · 2020-08-04T05:34:00

In order to give your service a UI you must add it to an account with a Allow Interaction With Desktop option set.

c# - Allow Windows service to interact with desktop - Stack Overflow[^]

Rather than duplicate the instructions, i provided this link for you. Hope it helps!

Anyway, you *should* be able to use Winforms from your service.

Window service equivalent for onhandlecreated & wndproc functions (from C#)

3 solutions

Solution 1

Solution 2

Solution 3

Add your solution here

Preview 0