Skip to content

fixing json config #1009

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Sep 8, 2016
Merged

fixing json config #1009

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
fe96b5a
fixing json config
mairaw Sep 6, 2016
401fcd0
fix future tense
mairaw Sep 6, 2016
bdc97c0
addressed feedback
mairaw Sep 7, 2016
8f6891f
Fixing emitEntryPoint description
mairaw Sep 7, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/core/tools/dotnet-build.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,11 +45,11 @@ compilation process to be incremental:
- not load compilation tools from PATH (for example, resgen, compilers)
- use only known compilers (csc, vbc, fsc)

In order to build an executable application, you need a special configuration section in your project.json file:
In order to build an executable application instead of a DLL, you need a [special configuration](project-json.md#emitentrypoint) section in your project.json file:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't "library" instead of "DLL" be better here, since applications in .Net Core are usually also DLL files?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Earlier in the topic we say that by default dotnet will build a binary with a DLL extension. I wanted to call out here explicitly how to change that and get an "exe" instead. @blackdwarf is this accurate?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mairaw yes and no. I think there are two questions here:

  1. How do I produce a runnable artifact, e.g. an application?
  2. How do I produce an "exe" file, that is, a native executable that I can "just run" on a given operating system?

For #1 above, it is true, you need the emitEntryPoint setting, but, as @svick mentions, you would still get a DLL.

For #2, the only way is to create a self-contained deployment.

Hope this makes sense. In general, I would go with @svick's suggestion and just say "library" instead of a "DLL".

Copy link
Contributor Author

@mairaw mairaw Sep 7, 2016 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the clarification @blackdwarf. So, do we also need to change the emitEntryPoint doc? It says: "true to create an executable; false to produce a .dll file. The default is false." From your explanation, I would get a DLL whether it's true or false.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, good point, that needs to be changed as well.


```json
{
"compilerOptions": {
"buildOptions": {
"emitEntryPoint": true
}
}
Expand Down