Skip to content
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] finalize paket integration for new .net sdk (msbuild 15) #2125

Closed
wants to merge 19 commits into from

Conversation

enricosada
Copy link
Collaborator

WIP, but

basically developing the final example in dev, so:

  • dev/.paket contains the boostrapper
  • dev/console contains a sample console app

NOTES

The Paket.Sdk is just for my easy of development, final is inside Paket nupkg

TODO

  • boostrapping with zero binaries
  • target to cleanup bootstrapped paket.exe
  • boostrap on first dotnet restore
  • paket restore called on dotnet restore after boostrapping
  • xplat (paket is an FDD = dotnet publish)
  • configurable paket version to restore on boostrap, with sane default
  • .cmd/.sh wrapper for boostrapping?
  • should work from dotnet msbuild so run .net core (dotnet build = dotnet msbuild /t:Build)
  • should work from msbuild so .net full (so call paket.exe)
  • use Paket nupkg instead of Packet.Sdk
  • integrate in current build script

@forki not lot of work todo left 😄

@enricosada
Copy link
Collaborator Author

I am trying different ways to integrate at restore step, each has a prop/cons ( I written something in dev/docs ).

I want to maintain the current nuget targets logic as much as possible, because make it easier for other commands (build/publish, the pack is not much useful for paket I think)

But override is hard because nuget target is imported AFTER our target file, becuase is inside the Sdk attribute.
And nuget target extensibility is limited (but we can completely override the nuget tasks)

Monday i’l try using Sdk attribute for paket too, so we can override single targets.

@forki
Copy link
Member

forki commented Mar 9, 2017

Hi what's the status here. Next week I'd like to go rc or even release paket 4.

@enricosada
Copy link
Collaborator Author

status is:

  • bad for deeper sdk integration, i cannot find yet the correct flow/targets
  • okish for bootstrapper

maybe i should split in two..

@enricosada
Copy link
Collaborator Author

closing because obsolete

@enricosada enricosada closed this May 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants