SA not accepting .Net Core service EXE. Claims 'File is not a managed .NET file'
ixm77
Posts: 6 New member
When publishing a .NET Core 3.1 service project to a local folder, I get both an EXE as well as a dll assembly (besides all the dependency dlls).
SA 6 is able to process the dll (and embed the dependencies) without a problem.
However, I'd like to protect the EXE as well. So when creating another SA project and browsing to the exe, an error pops with a title of 'Browse a .NET Assmbly' and text of 'File is not a managed .NET file'.
Is this a known issue?
SA 6 is able to process the dll (and embed the dependencies) without a problem.
However, I'd like to protect the EXE as well. So when creating another SA project and browsing to the exe, an error pops with a title of 'Browse a .NET Assmbly' and text of 'File is not a managed .NET file'.
Is this a known issue?
Tagged:
Answers