-
Notifications
You must be signed in to change notification settings - Fork 527
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.
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
DotnetRestore target failed during build #1995
Comments
We don't install the dotnet sdk during build yet. So you would have to Am 01.11.2016 05:14 schrieb "pengo98" notifications@github.com:
|
Sorry to bring up old comments, but this feels like an old discussion:
I think the conclusion is that it isn't simple black/white. One makes the builds more reproducible. The other one saves significant bandwidth and is faster, but the user needs to install it (+PATH). |
What I would love to see is the Paket build using it's own toolchain (Paket 4) as dogfooding. |
But we still need the dotnet sdk and therefore have this problem, don't we? |
yes but tbf the sdk download is probably the fastest in the whole chain. (first restore of .NET standard takes much more time) |
I think they bundle a lot of the stuff and extract it first time. If you mean Paket restore maybe we should do something similar? |
maybe later. At first I would just see Paket help building itself on coreclr |
so dotnetcli install seems to work on master now. can you please check? |
Looks like the latest restore doesn't expect JSON format anymore :) |
Yeah I guess that's one for tomorrow Am 01.11.2016 11:28 vorm. schrieb "Tomasz Heimowski" <
|
Question is if it's even possible to have net 45 + coreclr build in same Am 01.11.2016 11:57 vorm. schrieb "Steffen Forkmann" sforkmann@gmail.com: Yeah I guess that's one for tomorrow Am 01.11.2016 11:28 vorm. schrieb "Tomasz Heimowski" <
|
Sure, just set |
Btw abut install.
The test of build script should just invoke |
Yes but what about development? Vs will just break right? Am 01.11.2016 1:48 nachm. schrieb "Enrico Sada" notifications@github.com:
|
Pretty sure doesnt work atm From: Steffen Forkmann notifications@github.com Yes but what about development? Vs will just break right? Am 01.11.2016 1:48 nachm. schrieb "Enrico Sada" notifications@github.com:
You are receiving this because you were mentioned. |
So in other words: situation is currently worse than with preview 2 and project.json? We can no longer develop in VS and just have a few project.json files next to the fsproj. Since everything is in the same file and that file is not backwards compatible, we basically break everything. Damn |
@forki a bit too negative dont you think? 😄 So atm, we can use another fsproj next to original, like with For sure the starting point is having the projects working in the sdk from the cli (so restore/build/pack etc), and ide after that. As a note, we started a group to focus on contributing on netcore and the sdk http://fsharp.github.io/2016/10/31/dotnetcore_sdk_group.html for the full experience (so from templates to ide) for both new projects and existing projects. The group is about .net core AND sdk, that mean the new fsproj msbuild project system who replace project.json, because that's and important part of the sdk. |
That might be a solution. Will try tomorrow. Thx Am 01.11.2016 23:32 schrieb "Enrico Sada" notifications@github.com:
|
@forki : I believe I do have dotnet SDK installed on my machine so the DotnetRestore target should not need to run. Can you confirm the path of dotnet SDK? Is it "C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\ "?
Re above exception, which executable is it trying to launch? From build.fsx, it seems like it's looking for dotnet.exe. |
We didn't move off project.json just yet, not ready enough for us |
@yishaigalatzer still 1.0.0-preview3-003892 fails with dotnet restore on project.sjon files. is there a "backwards-compatible" command. Maybe restore2 or something? |
@pengo98 we want to make sure it's the right version... |
Looping in help |
@yishaigalatzer i'll send a pr soon |
Restore now takes msbuild project files as input, you could try putting a project file next to the project.json file and passing that to dotnet restore. It will then treat it as a UWP project instead of an xproj project.json. |
Ok updated f# integration to latest sdk drop ( https://github.com/dotnet/netcorecli-fsc/tree/master/examples/preview3 ). |
Just tried to do an
|
please use core3 branch |
Same problem, here the error message
And the log for completeness |
It seems that resolving the local dotnet core package isn't working in my environment. When I use the global installed dotnet preview 3 it works fine until it tries to restore the sub packages.
|
same problem goes on |
@rtarta which dotnet version do you have installed? |
Closing, now should work |
Description
I have been trying to build Paket solution using build.cmd that comes with the repo and the build fails at Target DotnetRestore complaining "Cannot start process because a file name has not been provided."
Repro steps
Clone repo
Run build.cmd from the command line.
Expected behavior
The build script should run successfully.
Actual behavior
I'm getting the following error.
Starting Target: DotnetRestore (==> Build)
restore C:\Users\nelson.lin\Source\Github\Paket\src\Paket.Core\Paket.Core\project.json
Running build failed.
Error:
System.Exception: Start of process failed. Cannot start process because a file name has not been provided.
at Fake.ProcessHelper.ExecProcessWithLambdas@79-16.Invoke(String message) in C:\code\FAKE\src\app\FakeLib\ProcessHelper.fs:line 79
at Fake.ProcessHelper.ExecProcessWithLambdas(FSharpFunc
2 configProcessStartInfoF, TimeSpan timeOut, Boolean silent, FSharpFunc
2 errorF, FSharpFunc2 messageF) in C:\code\FAKE\src\app\FakeLib\ProcessHelper.fs:line 79 at FSI_0005.Fake.DotNet.Cli.Dotnet(DotnetOptions options, String args) at FSI_0005.Fake.DotNet.Cli.DotnetRestore(FSharpFunc
2 setParams, String project)at FSI_0005.Build.clo@151-9.Invoke(String proj)
at Microsoft.FSharp.Collections.SeqModule.Iterate[T](FSharpFunc
2 action, IEnumerable
1 source)at FSI_0005.Build.clo@148-8.Invoke(Unit _arg1)
at Fake.TargetHelper.runSingleTarget(TargetTemplate`1 target) in C:\code\FAKE\src\app\FakeLib\TargetHelper.fs:line 492
Known workarounds
n/a
The text was updated successfully, but these errors were encountered: