Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can I publish .NET Core 3.0 app as FDD than FDE? #3686

Closed
xiaomi7732 opened this issue Oct 23, 2019 · 2 comments
Closed

How can I publish .NET Core 3.0 app as FDD than FDE? #3686

xiaomi7732 opened this issue Oct 23, 2019 · 2 comments

Comments

@xiaomi7732
Copy link

xiaomi7732 commented Oct 23, 2019

.NET Core 3.0 app will be published as FDE by default according to the docs.
What can I do to change the behavior back to deploy as FDD just like .NET Core 2.x? Ideally, is there any property to be set in the csproj file?

I am publishing assemblies that runs on both Linux and Windows. The target environment will have .NET Core runtime installed. FDD has been working well. There's no point for me to release an EXE when built on Windows.

@dagood
Copy link
Member

dagood commented Oct 25, 2019

Answered over at https://github.com/dotnet/cli/issues/12716#issuecomment-535331850:

Your app will still work as a FDD app. You can still run dotnet program.dll. The program.exe that is in the output can simply be ignored.

The type of app that gets built has not been changed.

If you don't want the exe generated because you don't want to pay the file cost for it, you can turn that off by setting <UseAppHost>false</UseAppHost>.

@dagood
Copy link
Member

dagood commented Oct 25, 2019

Duplicate of https://github.com/dotnet/cli/issues/12716

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants