Create NuGet package release

[rneatherway]

No description provided.

[baronfel]

Is the intent here to have a FsAutoComplete nuget package that just zips up all the outputs and makes them available via single-package download?

[rneatherway]

That might have been it, but honestly it is so long ago that I cannot remember why this would be useful.

[enricosada]

@baronfel ihmo the easier way to release FSAC will be:

• pack the fsac as .net global tool (so will bundle the .net core fsac) with /p:PackAsTool=true
• copy the published .NET FSAC inside the nupkg, in tools/net461/any, similar to tools/netcoreapp2.0/any
• publish that package to nuget org

that will allow to install fsac with dotnet tool install, or bundle in others editors extensions because is just a single zip package

example dotnet tool install Equinox.Tool -g who is a .net core tool + contains a net .exe:

• publish and pack commands https://github.com/jet/equinox/blob/41a28200aa98da95cc5cb773068196e0836f561a/build.proj#L23-L24
• include the net461 in the nupkg like https://github.com/jet/equinox/blob/41a28200aa98da95cc5cb773068196e0836f561a/tools/Equinox.Tool/Equinox.Tool.fsproj#L59-L65

[Krzysztof-Cieslak]

We should

1. Release LanguageServerProtocol.fsproj as NuGet package
2. Release FSAC.Core as NuGet package
3. Release FSAC as global dotnet tool (especially important for people that'd want to use LSP version with emacs/ST3/etc - right now suggestion for them is to build from master - look at instructions here https://github.com/emacs-lsp/lsp-mode#supported-languages)

[Krzysztof-Cieslak]

But we probably want to wait with releasing all that for solving FSAC ownership problem. CC: @ReedCopsey

[enricosada]

Meanwhile I’ll create the dotnet tool package ( I can add the net version inside there too) But probably we need one package per OS, and release the .net core as self contains (more MB and per OS) to use ReadyToRun (cross gen) who Speedo FCS quite a bit, because does AOT From mobile

…

-- Enrico Sada @enricosada

________________________________ Da: Krzysztof Cieślak <notifications@github.com> Inviato: giovedì, giugno 13, 2019 11:45 AM A: fsharp/FsAutoComplete Cc: Enrico Sada; Comment Oggetto: Re: [fsharp/FsAutoComplete] Create NuGet package release (#36) But we probably want to wait with releasing all that for solving FSAC ownership problem. CC: @ReedCopsey<https://github.com/ReedCopsey> — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#36>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AABD6K3WDJ3A5XNA66J4L6TP2IJLLANCNFSM4BJ5AP6A>.

[tani]

@enricosada @Krzysztof-Cieslak I could not found any packages about FSAC on nuget.org, Do you have any plan to upload these packages?

[baronfel]

Going to reopen this as we're not currently publishing packages to nuget right now of any kind.

[baronfel]

We're going to make an Ionide group in nuget and publish the initial version of this dotnet tool under that group. It's quite easy to add/transfer ownership of the package if it becomes necessary (ie if the fsharporg organization should be the maintainer, etc).

[baronfel]

This has been done, the package can now be fetched from Nuget. The command is dotnet tool install fsautocomplete, though of course it can be installed globally, locally, or to a specific path based on what the user wants.