How can we help you today? How can we help you today?

SA not accepting .Net Core service EXE. Claims 'File is not a managed .NET file'

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?
Ido Millet
0

Comments

3 comments

Sort by
  • ixm77
    Looks like support for .NET Core 3.1 is available only in later versions.  Thanks.
    ixm77
    0
  • Russell D
    Netcore 3.1 support was added in 7.4, so if you are able to test using that version please do so. If you have issues after upgrading, let us know!
    Russell D
    0
  • ixm77
    Turns out the EXE is just a "loader" for the dll. So given the older SA 6 is still able to process the .Net Core 3.1 service dll, consider the issue as resolved. 
    ixm77
    0

Add comment

Please sign in to leave a comment.