0

I have a Windows service built using .NET Framework (version 4.6.2). It was made using the "Windows Service (.NET Framework)" template in Visual Studio 2017. For reference, I followed this guide.

A custom installer will be made to install/update/maintain this Windows service on client machines. Here's an overview of the installer:

  • User enters some information into a form/UI.
  • Validate user input.
  • Place the Windows service project binaries in a user-specified directory.
  • Run the command to install the Windows service. It will use the Windows sc utility.
  • Create a registry key. Insert values into this registry key.
  • Ensure .NET Framework 4.6.2 is installed on the machine. Install it if it is not already installed.

As far as I can tell, when the service is started, .NET Framework 4.6.2 needs to already be installed on the machine for the service to work.

How do I make certain that the client's machine has .NET Framework 4.6.2 installed on it?

Also, will other versions of .NET Framework - for example version 4.8 - already installed on the machine cause issues?

I did some searching online, but haven't found any solutions for my situation. This solution only works if we decide to use the Visual Studio Installer project for our installer. Self-contained deployments apparently only work for projects based on .NET Core, not .NET Framework.

Max Jacob
  • 701
  • 1
  • 9
  • 20
  • I did something like this a couple years ago for an older project. I believe we basically whipped up a smaller helper program that was .NET 3.5 or 4.0 and included the actual .NET 4.X installer with it. The helper app checked the installed version of .NET, and launched the installer if the installed version was < 4.X. Something like that. I don't remember the exact process. – Broots Waymb Jan 22 '20 at 21:58
  • So in your case, you manually included the installer - such as [this](https://www.microsoft.com/en-us/download/details.aspx?id=53345) one - and invoked it as part of your regular installation process? – Max Jacob Jan 22 '20 at 22:06
  • Well it was sort of a different scenario. For new installs I believe we used InstallShield, which can enforce .NET version requirements for you. But for updates, we kicked off the helper app as part of the updater program's process, which did the dirty work of checking/updating .NET, then the updater program (not ours) rolled back/aborted if the newer .NET didn't install correctly. It was a very janky process... – Broots Waymb Jan 23 '20 at 14:05

1 Answers1

0

Although we haven't yet implemented our custom installer, after some research, here is what we will most likely do:

  • Include the offline installer for .NET Framework (in our case, we need version 4.6.2) within our custom installer.

  • Have our custom installer check for an existing version of .NET Framework. See this document for details on determining an installed version of .NET Framework.

    • If the client has .NET Framework version 4.6.2. (or greater) installed, then move on with the installation process.

    • If the client has an older version of .NET Framework installed, then ask them if they want to update to version 4.6.2. If they decline, abort the custom installer. If they choose to update to .NET Framework version 4.6.2, then we will invoke the offline installer. See the basic code example below invoking the offline installer:

      // NOTE: This code is just a crude example.

// Invoke the offline installer.
System.Diagnostics.Process process = new System.Diagnostics.Process();
System.Diagnostics.ProcessStartInfo startInfo = new System.Diagnostics.ProcessStartInfo();
startInfo.WindowStyle = System.Diagnostics.ProcessWindowStyle.Hidden;
startInfo.FileName = "cmd.exe";
startInfo.Arguments = "/C path\\to\\offline\\installer\\NDP462-KB3151800-x86-x64-AllOS-ENU.exe";
process.StartInfo = startInfo;
process.Start();

process.WaitForExit();

// Handle the exit code.
if (process.ExitCode == ...)
{
    ...
}

References

  • This document provides an introduction to redistributing the .NET Framework.
  • This document provides details on redistributing the .NET Framework.
  • This document contains information about minimum system requirements for .NET Framework.
  • Although more IT-oriented, this tutorial and this tutorial contain useful details about installing .NET Framework.

Related

The following was found during some of my testing/research:

  • By default, these operating systems have the following versions of .NET Framework installed:
    • Windows 7 SP1 – .NET Framework version 3.5.30729.5420
    • Windows 10 November 2019 Update (Version 1909) – .NET Framework version 4.8
    • Windows Server 2012 R2 Standard (Version 6.3.9600) – .NET Framework version 4.5.1
    • Windows Server 2019 (Version 10.0.17763; a.k.a. Version 1809) – .NET Framework version 4.7.2
  • With recent updates (circa February 2020), these operating systems have the following versions of .NET Framework installed:
    • Windows 7 SP1 – .NET Framework version 4.8
    • Windows 10 November 2019 Update (Version 1909) – .NET Framework version 4.8
    • Windows Server 2012 R2 Standard (Version 6.3.9600) – .NET Framework version 4.8
    • Windows Server 2019 (Version 10.0.17763; a.k.a. Version 1809) – .NET Framework version 4.7.2

Troubleshooting

  • This document contains information on how to troubleshoot .NET Framework installation/un-installation.
  • This document contains information on troubleshooting an error related to starting an application dependent on .NET Framework.
Max Jacob
  • 701
  • 1
  • 9
  • 20