Cannot build a project within VS as being blocked.

[Former Member]

I am unable to build a solution within Visual Studio, where other members of the team can. I get the following error:

C:\Users\user.name\.nuget\packages\postsharp\6.6.10\build\PostSharp.targets(381,5): error PS0240: Exception in .NET strong name API invocation. Error while getting key info for 'C:\github\ems-execution-management-system\Proquote.TechnologyPlatform\Signing\ProquoteKeyFile.snk': Strong name key container not found. (Exception from HRESULT: 0x8013141C).

I have excluded C:\github, but still get the issue. 

If you google the error, there are a few articles on how this can be Mcafee blocking it.

This stackoverflow article suggests it might be McAfee: https://stackoverflow.com/questions/62678594/postsharp-throws-system-runtime-interopservices-comexce...

I have created a VM in a test environment to confirm this and the project builds fine. Although this cannot be a long term solution. My colleagues that are able to build the solution don't have McAfee installed, so it feels like it is a McAfee issue. Please can you help or advise on what i need to exclude via EPO? 

ePO Build: ePolicy Orchestrator 5.9.0 (Build 732)

Endpoint Sec version 10.6

Many thanks

Dean 

[cdinet]

I am going to move this over to the ENS team so they can better assist.  If you look at your access protection logs in ens, you might find some blocking.  Otherwise there might be other necessary exclusions needed.  

[AdithyanT]

Hi @Former Member,

Thank you for your post. I would recommend isolating the component first to identify where you should be adding the exclusions.

• For all Endpoint Security platforms:
  1. Disable On-Access Scan. If the Build runs fine, re-enable On-Access Scan and then disable the following options and test after each. Otherwise, continue to the next step.
     • Scan Boot Sectors
     • Scan Processes on enable
     • Scan Trusted installers (if there is an application installation involved)
     • ScriptScan
     • Scan on Network Drives
     • Scan when writing to disk
     • Scan when reading from disk
     • Find unknown unwanted programs and trojans
     • Find unknown macro threats
     • Scan inside archives
     • Decode MIME encoded files
     • Detect unwanted programs
  2. Disable Access Protection. If the build works, re-enable Access Protection and then disable blocking and reporting on each of the Access Protection Rules and test after each. Otherwise, continue to the next step.
  3. Disable Exploit Prevention. If the build works, re-enable Exploit Prevention and then disable each signature and Application Protection Rule and test after each.

Once we figure which component it is, we can add the exclusion accordingly. To gain assistance on this over remote, you can alternatively log a support ticket with us and we will be happy to assist you on the same. Sincerely hope this helps!

[Former Member]

Thank you for the quick response, however I went through all of those 3 turning them off and it still didn't work. 

[AdithyanT]

Hi @Former Member,

Thank you for the update. Quite Odd! can you try removing Endpoint Security just to be sure? Please uninstall Endpoint Security and let us know if the issue still exists? If the issue goes away, I would recommend a Support ticket!