Description

Updates to SharpHound to check the installed version of .Net Framework to ensure it meets our target. If the system does not, a log will be created and SharpHound will exit.

Motivation and Context

This PR addresses: BED-5936

This change was recommended because some users are on older versions of Windows which can cause issues while running the application since we target a newer version of .Net Framework.

How Has This Been Tested?

This was tested by running SharpHound on a system with .Net Framework 4.7.2 and trying to run the software on a system with .Net Framework 4.6.2. The software was unable to run on the latter system. This system was then updated by installing .Net Framework 4.7.2, which allowed SharpHound to run.

In both the system that could initially run the updated application and the system that was updated to be able to run SharpHound, a collection was run and the data was successfully ingested in a local BloodHound Enterprise Instance.

Screenshots (optional):

The new error log

Types of changes

• Chore (a change that does not modify the application functionality)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist:

• Documentation updates are needed, and have been made accordingly.
• As a note, I could not find any documentation specifying the necessary version of .Net Framework on the system. Should there be place for this?
• I have added and/or updated tests to cover my changes.
• All new and existing tests passed.
• My changes include a database migration.