dotnet new / restore / publish do not generate EXE file
See original GitHub issueI would like to generate a standalone exe file when publishing the app. The app needs to consume the latest post-1.1 bits (e.g. 1.2.0-beta-249##). Despite the csproj file having <OutputType>Exe</OutputType> I always get a .dll instead of .exe
Steps to reproduce
install the latest tooling create folder foo dotnet new dotnet restore dotnet build dotnet publish (or dotnet publish -r win7-x64)
Expected behavior
foo.exe file gets generated in the published folder
Actual behavior
foo.dll gets generated
Specifying -r runtime_id used to do the trick but not anymore.
Environment data
dotnet --info
output:
.NET Command Line Tools (1.0.0-preview5-004478)
Product Information: Version: 1.0.0-preview5-004478 Commit SHA-1 hash: 4d3e2872fe
Runtime Environment: OS Name: Windows OS Version: 10.0.14393 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\1.0.0-preview5-004478
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (8 by maintainers)
@GuardRex fyi the locals command also works using the included
dotnet nuget
command. No need to download the nuget cli for that 😉Thanks, I’ll give it a try.