Skip to content

Commit

Permalink
merging #227 README
Browse files Browse the repository at this point in the history
  • Loading branch information
agracio committed Oct 25, 2024
1 parent d20dc28 commit 1a4acbc
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -777,7 +777,9 @@ set EDGE_APP_ROOT=c:\DotNet\MyProject\bin\Release\netstandard1.6
node app.js
```

Edge.js also supports running published .NET Core applications on servers that do not have the .NET Core SDK and CLI installed, which is a common scenario in production environments. To do so, the `.csproj` for your application should meet the following requirements:
When calling a compiled assembly, Edge.js supports running with only the .NET runtime installed (and not the SDK or CLI). In this case a `appname.runtimeconfig.json` has to be created when building the project an present in your `EDGE_APP_ROOT` directory. `<GenerateRuntimeConfigurationFiles>true</GenerateRuntimeConfigurationFiles>`should be present under `<PropertyGroup>` in your `.csproj`file to create this file.

Edge.js also supports running published .NET Core applications on servers that do not have the .NET Core SDK and CLI or .NET runtime installed, which is a common scenario in production environments. To do so, the `.csproj` for your application should meet the following requirements:

1. It should target the `netcoreapp2.x` or `netstandard2.0` framework moniker.
2. It should reference `Microsoft.NETCore.DotNetHost` and `Microsoft.NETCore.DotNetHostPolicy`. This is required so that the publish process can provide all the native libraries required to create a completely standalone version of your application.
Expand Down

0 comments on commit 1a4acbc

Please sign in to comment.