Nuget Packages

[Cris1401]

Hello, is this project available at nuget? That would be great. Thanks

[MaxKsyunz]

Hi @Cris1401.

Publishing opensearch .net client on nuget.org is being worked on. Please, see #14 for details.

In the meantime, you can use a release candidate build from this workflow.

[Jubilex]

What is the best way to include the release candidate nupkg in my project? It is a lambda project which using github webhooks for CI/CD and Codepipeline to build. I have found no way, short of hosting a nuget package server of referencing the nupkg in my code locally. Is there something I am missing?

[MaxKsyunz]

Hi @Jubilex, yes, at the moment your options are to either host the files yourself temporarily or add them to your repository.

[Jubilex]

That is VERY helpful, thank you for taking the time to offer this solution. Steve

…

On Wed, May 18, 2022 at 12:44 PM Dan Spiteri ***@***.***> wrote: @Jubilex <https://github.com/Jubilex> there is another solution, (and its how I currently workaround this issue) 1. Clone/Download a Zip of this repository, you want the contents of "packages" folder somewhere either within your solution's folder, or your somewhere in your system - if it's a git hosted project, obviously within your repo is best. I named my folder "lib". 2. Create/edit a NuGet.config file in the same folder as your .sln and add "lib/" as a package source. <?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <add key="sln-local" value="lib/" /> </packageSources> </configuration> You should end up with something like this: [image: image] <https://user-images.githubusercontent.com/983207/169107565-39aabaa9-cfdf-4211-acdc-f9e663ac1ff4.png> 1. Now you should be able to find + reference the packages from the nuget tool within your IDE, and have it also work via CI/CD etc :) Hope this helps! — Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWHFACLJOJDB4YBSH6SP2LVKUT6VANCNFSM5UCF76ZQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[TruDan]

I wrote it as I was trying it, after I realised that actually I had to compile the solution first (from the solution folder, I used `dotnet pack -o <my_lib_dir>` then I could add the package 'Osc' On Wed, 18 May 2022, 20:21 Steven Callahan, ***@***.***> wrote:

…

That is VERY helpful, thank you for taking the time to offer this solution. Steve On Wed, May 18, 2022 at 12:44 PM Dan Spiteri ***@***.***> wrote: > @Jubilex <https://github.com/Jubilex> there is another solution, (and its > how I currently workaround this issue) > > 1. Clone/Download a Zip of this repository, you want the contents of > "packages" folder somewhere either within your solution's folder, or your > somewhere in your system - if it's a git hosted project, obviously within > your repo is best. I named my folder "lib". > 2. Create/edit a NuGet.config file in the same folder as your .sln and > add "lib/" as a package source. > > <?xml version="1.0" encoding="utf-8"?> > <configuration> > <packageSources> > <add key="sln-local" value="lib/" /> > </packageSources> > </configuration> > > You should end up with something like this: > [image: image] > < https://user-images.githubusercontent.com/983207/169107565-39aabaa9-cfdf-4211-acdc-f9e663ac1ff4.png > > > 1. Now you should be able to find + reference the packages from the > nuget tool within your IDE, and have it also work via CI/CD etc :) > > Hope this helps! > > — > Reply to this email directly, view it on GitHub > < #38 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAWHFACLJOJDB4YBSH6SP2LVKUT6VANCNFSM5UCF76ZQ > > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHQBJ4FTI2KLN2YB36TE6LVKUYJPANCNFSM5UCF76ZQ> . You are receiving this because you commented.Message ID: ***@***.***>

[cray2015]

@TruDan u didnt had to do it. all you had to do was to download the nuget package from the build workflow mentioned in the first thread of this discussion and then add the local location of this package in dotnet nuget sources
dotnet nuget add source /home/your_username/Downloads/osc_nuget_packages/ -n custom_nuget_packages
change the source to windows directory style while doing this on windows or you can use the user interface of Visual Studio

Tools>Nuget Package Manager>Package Manager Settings>Package Sources.

Refer the below Link:
https://docs.microsoft.com/en-us/nuget/consume-packages/install-use-packages-visual-studio#package-sources

then you can use it like a regular package from Nuget window. Just change the Package Source dropdown to "All"

[BaldGuitarist]

This works great. I'm curious as to when you plan to have the nupkg on nuget?

[anirudha]

This works great. I'm curious as to when you plan to have the nupkg on nuget?

We should have the packages In nuget soon.

[nbpeth]

We should have the packages In nuget soon.

terrific - this would be very helpful; will be watching

[dblock]

Is #14 a dup?

[PaulDMendoza]

This works great. I'm curious as to when you plan to have the nupkg on nuget?

We should have the packages In nuget soon.

What is your definition of "soon"? It's been 2 weeks since you said soon. We really need this package in nuget.

[GiorgioG]

@PaulDMendoza We decided to skip OpenSearch altogether and use ElasticSearch - there's no point in trying to use a client/package that isn't well supported IMO.

[dblock]

I am equally frustrated by this situation. Please follow opensearch-project/opensearch-build#2051.

[anirudha]

I posted the current status on the release thread, but I also want to acknowledge, and apologize for failing to provide a regular status update earlier. Thank you for your patience.

opensearch-project/opensearch-build#2051 (comment)

[MaxKsyunz]

The packages have been released -- https://www.nuget.org/profiles/opensearchproject