This repo is the official home of .NET on GitHub. It's a great starting point to find many .NET OSS projects from Microsoft and the community, including many that are part of the .NET Foundation.
I'm trying to publish a .net 6.0 console app to win-x64, osx-x64 and osx-arm64 using my csproj and various profiles defined before but all indicating using "Release", "ProduceSingleFile" and "SelfContained".
I've added the following inside my csproj:
`
Exenet6.0win-x64;osx-x64;osx-arm64
`
Please not the -c Release in the osx publish. I do not add them when publishing to osx... the publish process ALWAYS tries to retrieve singlefilehost from the DEBUG folder instead of the RELEASE one.
I'm trying to publish a .net 6.0 console app to win-x64, osx-x64 and osx-arm64 using my csproj and various profiles defined before but all indicating using "Release", "ProduceSingleFile" and "SelfContained".
I've added the following inside my csproj:
`
`
Please not the -c Release in the osx publish. I do not add them when publishing to osx... the publish process ALWAYS tries to retrieve singlefilehost from the DEBUG folder instead of the RELEASE one.
Adding -c Release allows bypassing the issue.