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

CefSharp on Nuget #123

Closed
computersrmyfriends opened this issue Apr 25, 2013 · 7 comments
Closed

CefSharp on Nuget #123

computersrmyfriends opened this issue Apr 25, 2013 · 7 comments

Comments

@computersrmyfriends
Copy link

Please upload cefsharp on nuget so that it's more easier to use.

Thanks

@ataranto
Copy link
Contributor

I don't have any plans to distribute CefSharp on nuget

@damianh
Copy link

damianh commented May 29, 2013

+1 NuGet package please

@adamralph
Copy link

+1 here too

@ataranto would you not even consider a pull request which adds package creation?

@kevfromireland
Copy link

The primary reason for my fork (on the Red Gate organization page) is to have NuGet support and strong naming. I would love to be able to more closely track your branch but NuGet and Strong Naming are unfortunately things that I need.

+1 on NuGet to make it easier for others to consume this.

@chillitom
Copy link
Contributor

@kevfromireland Per is on it I believe, but you should def feel free to submit a pull request with the work you've done, CefSharp is very much a scratch your own itch project, all hands welcome aboard.

@perlun
Copy link
Member

perlun commented Jul 25, 2013

Confirmed - I have actually also made a (unofficial/not-yet-so-public 😉) NuGet package for WPF. We should definitely do this, it makes consuming CefSharp from a WinForms of WPF application a lot easier.

As @chillitom says - @kevfromireland, please submit a pull request. I would be very interesting in getting this merged, especially if you have done it in the proper way (by using a custom MSBuild file and copying in the libcef.dll et al into bin\Debug and bin\Release post-build).

@perlun perlun reopened this Jul 25, 2013
@perlun
Copy link
Member

perlun commented Jul 25, 2013

I actually already created a new issue for this in another repo, which I've now copied here: #137. Let's close this one and continue the discussion there, please.

@perlun perlun closed this as completed Jul 25, 2013
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

No branches or pull requests

7 participants