Why does entry-points.json disappear after publishing?

Hello all,

I have noticed when working on projects, I will often have an entry-points.json file. After I publish from Studio to Orchestrator, this file disappears. Why is this, and why does my project work fine whether or not this file is in the project?

I know the file points out the entry-workflow for the project, but why does the project still run without it?

Thank you

Hello @edevries ,

When you publish to Orchestrator, Studio compiles and packages the project into a .nupkg file. During that packaging step:

  • The entry point information gets embedded directly into the package metadata (project.json and the NuGet package manifest).
  • The entry-points.json file is therefore no longer needed as a standalone file β€” its job is done and the data lives elsewhere in the package.
  • Orchestrator reads entry point info from the package metadata, not from a loose JSON file.

see the below project.json file which i have downloaded from orchestrator lookslike:

So it’s not really disappearing β€” it’s being absorbed into the compiled output.

Thanks,
Karthik

I appreciate the answer. My team recently moved from Git to TFS (yeah I know weird switch) , and it made me notice this stuff.