DEV Community

David Sugar
David Sugar

Posted on

Deploying services on Windows

Services are also often headless daemons, that is, they have no user visible ui, and are meant to be running all the time. While I used to write very highly portable code for telephony services, I have been writing services (often in C++) only for posix and embedded targets for at least a decade now.

It's hard for me to find a use case for running windows as a services platform. But I was never closed to the idea of running telephony services on windows if a plausible use case can be suggested. For my own code, in most cases, it would be changing my main.cpp to conditionally compile as a windows system service rather than just managed thru posix signal handlers. Other changes are probably much smaller.

My current telephony applications build with the eXosip library. This does build and runs on windows, and I vendor it in my packages so it can build locally without trying to get it to externally build in something like vcpkg, so it's easy to carry and build that too. Actually, I also use eXosip for client telephony applications for this reason, too, but those I tend to build with Qt, which already is fully portable.

Do your career a big favor. Join DEV. (The website you're on right now)

It takes one minute, it's free, and is worth it for your career.

Get started

Community matters

Top comments (0)

👋 Kindness is contagious

Discover a treasure trove of wisdom within this insightful piece, highly respected in the nurturing DEV Community enviroment. Developers, whether novice or expert, are encouraged to participate and add to our shared knowledge basin.

A simple "thank you" can illuminate someone's day. Express your appreciation in the comments section!

On DEV, sharing ideas smoothens our journey and strengthens our community ties. Learn something useful? Offering a quick thanks to the author is deeply appreciated.

Okay