-
Notifications
You must be signed in to change notification settings - Fork 525
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
WIP Make Paket work with dotnet cli preview3 #1977
Conversation
forki
commented
Oct 24, 2016
•
edited
Loading
edited
- - Make "paket install" hook into MSBuild 15 / dotnet cli preview3 restore
- - Make Paket restore it's own PaketRestoreTask.dll
- - Do not emit dll references for MSBuild 15 projects
- - Use magic mode
- - Make everything work in ionide
- - Make Paket create it's own Nuget.Config or hook into that in MSBuild
- - Convert from Nuget should read / remvoe PackageReferences from *proj - (@theimowski ?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
build.sh
Outdated
exit_code=$? | ||
if [ $exit_code -ne 0 ]; then | ||
certificate_count=$(certmgr -list -c Trust | grep X.509 | wc -l) | ||
if [ $certificate_count -le 1 ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we might still need this, just later at the paket.exe call...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
src/Paket.Core/LockFile.fs
Outdated
for p in g.NugetPackages do | ||
let k = groupName,p.Name | ||
if usedPackages.ContainsKey k then | ||
failwithf "Package %O is referenced more than once in %s within group %O." p.Name referencesFile.FileName groupName | ||
usedPackages.Add(k,p) | ||
|
||
g.NugetPackages | ||
|> List.iter (fun package -> | ||
|> List.iter (fun package -> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
|
||
namespace Paket.Build.Tasks | ||
{ | ||
public class PaketRestoreTask : Task |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some crasy thinking: Would it make sense to think about extension points in paket?
Considering all those different use cases we might have soon (dotnetcore, toml, legacy, fable?) shouldn't we try to get things like these out of paket core into modules or something like that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure. bringe them on
Re convert - there's no packages.config anymore, but rather every dep is moved to *proj? Is it a 1-1 mapping? |
It's looking like this now:
|
I can give it a try, but can take a week or two - little spare time right now |
yeah don't worry. no need to hurry |
which dotnet core build you're using? Is it 1.0.0-preview3-003884? With the latest dotnet (https://dotnetcli.blob.core.windows.net/dotnet/Sdk/rel-1.0.0/dotnet-dev-win-x64.latest.zip), when I try to repro your showcase, I get |
@theimowski you must run paket install once before you can restore. |
Thanks, that was the case. Also turns out, in latest dotnet core there's no more "3" suffix for commands https://github.com/dotnet/cli/issues/4205 |
I'm hacking around convert - pushing changes directly to this branch - is it fine with you? |
Yes that's fine. Maybe we need another feed. @enricosada? |
https://github.com/dotnet/netcorecli-fsc/blob/master/examples/preview3/lib/NuGet.Config Sent from mobile From: Steffen Forkmann [email protected] Yes that's fine. Maybe we need another feed. @enricosadahttps://github.com/enricosada? You are receiving this because you were mentioned. |
Also the dotnet sdk feeds https://github.com/dotnet/cli/blob/rel/1.0.0/NuGet.Config Sent from mobile From: Steffen Forkmann [email protected] You are receiving this because you were mentioned. |
@theimowski we can consume v3 API. just make sure all the nuget feeds are added to paket.deps and I think it's without the last part of the url |
yeah sorry my fault - didn't spot last @enricosada comment. It seems it's resolving deps now with those 4 additional feeds, but taking ages... |
@theimowski welcome to the brave new world of dotnet shipping via nuget |
Huh...
and that's for just 3 deps:
|
how fast is second update? |
you mean running now |
Cold cache. And other packages are from nuget.orghttp://nuget.org so faster. Sent from mobile From: Tomasz Heimowski [email protected] Huh... c:\sandbox\core3paket (master)
and that's for just 3 deps: source https://www.nuget.org/api/v2 You are receiving this because you were mentioned. |
@theimowski no --force would take same time (since it skips cache). just run paket update |
How does it work now? Paket downloads the nupkgs to ./packages dir and then copies them to %HOME%.nuget.packages ? |
Currently we download to both locations. Am 03.11.2016 14:27 schrieb "Tomasz Heimowski" [email protected]:
|
ok i started the work in #2004 |
collect multiple install errors before failing
version bump
# Conflicts: # RELEASE_NOTES.md # src/Paket.Bootstrapper/Properties/AssemblyInfo.cs # src/Paket.Core/AssemblyInfo.fs # src/Paket.PowerShell/AssemblyInfo.fs # src/Paket/AssemblyInfo.fs
# Conflicts: # RELEASE_NOTES.md # src/Paket.Bootstrapper/Properties/AssemblyInfo.cs # src/Paket.Core/AssemblyInfo.fs # src/Paket.PowerShell/AssemblyInfo.fs # src/Paket/AssemblyInfo.fs