forked from heroku/dotnet-buildpack
-
Notifications
You must be signed in to change notification settings - Fork 11
Open
Description
Structure:
FooBar
FooBar.Test (depends on FooBar)
Output:
-----> .NET Core app detected
remote: Found 2 project.json files
remote: Building FooBar.Test/project.json
remote: log : Restoring packages for FooBar.Test/project.json...
[...]
remote: log : Writing lock file to disk. Path: FooBar.Test/project.lock.json
remote: log : FooBar.Test/project.json
remote: log : Restore completed in 7728ms.
remote: Publishing FooBar.Test for .NETCoreApp,Version=v1.1
remote: Project FooBar does not have a lock file. Please run "dotnet restore" to generate a new lock file.
remote: Project FooBar does not have a lock file. Please run "dotnet restore" to generate a new lock file.
remote: Published 0/1 projects successfully
remote: ! Push rejected, failed to compile .NET Core app.
remote:
remote: ! Push failed
We have 2 different concepts here:
- dotnet restore
- dotnet publish
What you dotnet restore is not necessary what you publish.
In this example I want to restore both FooBar and FooBar.Test, run the tests on Heroku and publish FooBar.
Currenlty, if there is no .deployment file, the buildpack restore and builds the first project.json found.
What about simply dotnet restore everything? Is there a need for restoring only a list of particular projects?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels