{"id":6607,"date":"2019-04-02T08:36:27","date_gmt":"2019-04-02T15:36:27","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=6607"},"modified":"2025-11-24T11:36:18","modified_gmt":"2025-11-24T19:36:18","slug":"vs-custom-windows-service","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/vs-custom-windows-service\/","title":{"rendered":"Why Should I Buy AlwaysUp Instead of Writing My Own Windows Service?"},"content":{"rendered":"
\"Why<\/div>\n

AlwaysUp was created to solve a simple problem. How do you make an existing executable run all the time, despite reboots, crashes and other annoying interruptions?<\/b><\/p>\n

To solve the problem, AlwaysUp leverages Microsoft’s technology of choice for 24\/7 operation — the Windows Service<\/a>. A service typically starts at boot and chugs away, uninterrupted, while your computer is on.<\/p>\n

More specifically, AlwaysUp is a service wrapper<\/a>.<\/p>\n

When you configure your application with AlwaysUp, a true\/native Windows Service is installed. And when that service is run, AlwaysUp intercepts the calls from the Windows Service Control Manager (SCM) and passes them on to your program.<\/p>\n

But the service wrapper approach is not the only way to solve the problem of 24\/7 operation. Why not roll up your sleeves and write some C#, VB.Net or C++ code to make your application itself a Windows Service?<\/p>\n

You should certainly entertain that option — especially if you are an experienced developer with access to your application’s source code. However, here are five questions to consider before going down that road:<\/p>\n

\n
\n
\"\"<\/a><\/div>\n<\/div>\n

1.  Do you have the time to build a first-rate solution?<\/h2>\n
\"Use<\/a><\/div>\n

Does your organization employ a competent, professional development team? If so, they should be smart enough to develop a Windows Service. After all, it’s not rocket science.<\/p>\n

But how long will it take<\/b> your team to create a solution that you and your business will be proud of?<\/p>\n

To be successful, you and your team must:<\/p>\n

    \n
  1. \n

    Learn<\/b> the Windows Services architecture<\/p>\n<\/li>\n

  2. \n

    Write<\/b> the initial\/prototype code (in C#, VB.Net or C++)<\/p>\n<\/li>\n

  3. \n

    Harden<\/b> the new code for production use (focusing on security, 24\/7 reliability, logging, etc.)<\/p>\n<\/li>\n

  4. \n

    Test\/certify<\/b> the code on all current variations of Windows (including Windows 10, 8, 8.1, 7 and Windows Server 2019, 2016, 2012, 2012 R2, 2008, 2008 R2)<\/p>\n<\/li>\n<\/ol>\n

    As you know, producing great software is not trivial — especially when commercial deadlines are involved!<\/p>\n

    AlwaysUp costs money but it is ready right now. Not next week, not next month — today<\/b>.<\/p>\n

    \n
    \n
    \"\"<\/a><\/div>\n<\/div>\n

    2.  Is coding a Windows Service the best way to spend your limited development resources?<\/h2>\n
    \"Be<\/a><\/div>\n

    Even if converting your application into a Windows Service is important, it is probably one of many high-priority items on your ambitious feature list. Might any of the other projects yield a higher ROI<\/b>?<\/p>\n

    The days (and weeks) spent learning the Windows Services API and crafting secure, robust code that works flawlessly on all versions of Windows won’t come for free. What other features could your developers be implementing during that time?<\/p>\n

    What high-priority work<\/b> will you have to delay<\/b> as your developers dive into the wild world of Windows Services?<\/p>\n

    Be mindful of lost opportunities as you deviate from your core competencies.<\/p>\n

    \n
    \n
    \"\"<\/a><\/div>\n<\/div>\n

    3.  Are you willing to continue investing in your Windows Services custom code?<\/h2>\n

    This article on software maintenance<\/a> highlights the dominant cost of custom software over time — ongoing maintenance.<\/p>\n

    \"Software<\/a><\/div>\n

    First, there will be the inevitable bugs in your new code<\/b>. It will take time and effort to identify and eliminate those self-inflicted problems as your code matures.<\/p>\n

    But beyond the home-grown defects, every patch from Microsoft brings the risk of “breakage”.<\/p>\n

    For example, Windows 10 build 1803 crippled access to Session 0<\/a>. This was a seismic event for some legacy software, which can no longer show a GUI on that version of the OS.<\/p>\n

    The sad truth is that developers operate in an environment of constant change — not always for the better.<\/p>\n

    Of course, AlwaysUp is subject to the same shifting sands. We too can be caught off guard by the little “surprises” that the folks in Redmond occasionally deliver.<\/p>\n

    But we are experts in Windows Services<\/b>. And our team tests each major release of Windows<\/b> before it available to the general public. <\/p>\n

    That expertise and vigilance enables us to identify and solve problems very quickly — before our customers become aware of them.<\/p>\n

    As a result, AlwaysUp is rock solid. When you deploy AlwaysUp, you automatically benefit from 15 years of commercial operation<\/b> and more than 80,000 installations<\/b> on physical and virtual machines across the globe.<\/p>\n

    \n
    \n
    \"\"<\/a><\/div>\n<\/div>\n

    4.  Do you need failure protection? Email notifications? Advanced Windows Service features?<\/h2>\n
    \"Do<\/a><\/div>\n

    Converting your application into a Windows Service is a great step forward, but AlwaysUp offers much more — to get you to 100% uptime.<\/p>\n

    For example, AlwaysUp can:<\/p>\n