You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This buildpack will be used if there are one or more `project.json` files in the pushed application.
16
+
This buildpack will be used if there are one or more `project.json` files in the pushed application, or if the application is pushed from the output directory of the `dotnet publish` command.
17
17
18
-
Also make sure the application includes a `kestrel` or a `web` command and the corresponding Microsoft.AspNet.Server.Kestrel dependency because the buildpack will use [Kestrel][] to run the application.
19
-
20
-
Use a `global.json` file to specify the desired DNX version if different than the latest stable beta release. Use a `NuGet.Config` file to specify non-default package sources.
18
+
Use a `NuGet.Config` file to specify non-default package sources.
21
19
22
20
For a basic example see this [Hello World sample][].
23
21
22
+
## Legacy DNX support (used for RC1 apps)
23
+
24
+
With the introduction of support for the Dotnet CLI in buildpack version 0.8, apps which relied on the older DNX toolchain will no longer work with the current buildpack. If you need to keep your app running on DNX for now until you can update it to use the Dotnet CLI, use the following command:
Keep in mind that this support provided to allow users time to update their apps to use the Dotnet CLI, and you should switch to using the main branch of the buildpack (using the command further above) as soon as possible.
31
+
24
32
## Disconnected environments
33
+
25
34
The binaries in `manifest.yml` can be cached with the buildpack.
26
35
27
-
Applications can be pushed with their other dependencies after "publishing" the application like `dnu publish` or `dnu publish --runtime ~/.dnx/runtimes/dnx-coreclr-linux-x64.1.0.0-beta7`. Then push from the `bin/output` director.
36
+
Applications can be pushed with their other dependencies after "publishing" the application like `dotnet publish`. Then push from the `bin/<Debug|Release>/<framework>/publish` directory.
28
37
29
38
## Building
30
39
@@ -57,11 +66,11 @@ These steps only apply to admins who wish to install the buildpack into their Cl
57
66
5. Use in Cloud Foundry
58
67
59
68
Upload the buildpack to your Cloud Foundry and optionally specify it by name
0 commit comments