[vlc-devel] libvlc on NuGet

[Damien]

Hi Jeremy,

I really like your lib because it works very well on windows, and it "just
works".

I think including vlc in nuget is a bad idea : it will make a really big
package, if you plan to include both x86 and x64.
Also how to choose which version of vlc to use, and about updates. What
about deployment of many applications on same computer, there would be many
duplicated files on disk...

Making devs for other platforms is a really good idea. You can develop
targeting netstandard1.4 I think, netstandard2.0. And you should be anycpu,
not x86 or x64.
Also, you will have to rewrite your code to remove windows specific APIs,
or add a way to properly detect platform and do the stuff accordingly.
For example, I would be happy to use your lib on Linux arm (raspberry pi)
with dotnet core 2.0.

And as bonus points, you may start adding vlc 3 APIs (from vlc git).

Thanks for reading :)

Damien

Le 16 août 2017 18:15, "Jeremy Vignelles" <jeremy.vignelles at dev3i.fr> a
écrit :

> I just saw that my previous mail was sent in text/html rather than
> plain/text. Apologies.
>
> Below is a version of the previous mail:
>
> > Hi,
> >
> > I am contributing to an open source VLC wrapper for .net
> (ZeBobo5/Vlc.DotNet).
> >
> > The current process of using the library for a .net project is:
> >
> > - Install Vlc.DotNet through the NuGet package manager.
> >
> > - Download manually and install Vlc libraries from the official website.
> >
> > - Configure the project to set the correct path of the Vlc library,
> depending on where you installed it.
> >
> > I would like to simplify that process by adding the native libvlc
> files to NuGet, so that they can be installed and the project configured as
> needed.
> >
> > I could package it by myself, push it to NuGet and create Yet Another
> LibVlc Distribution, but I like standard things, especially for production.
> That's why I think that would be better to have a "VideoLan" package, built
> each time a VLC is out and that is pushed to NuGet. I can help for that.
> >
> > What would involved:
> >
> > - Setup a build environment (could be a linux docker image I suppose,
> based on microsoft/dotnet image)
> >
> > - Write the .nuspec file that contains the package metadata
> >
> > - Create a "videolan" account on NuGet
> >
> > - Wire things up so that:
> >
> >    - The vlc release is downloaded
> >
> >    - The release is extracted and files are copied next to the
> .nuspecfiles
> >
> >    - `dotnet pack` is called with the package version as an argument
> (prereleases can be published with a x.y.z-beta1)
> >
> >    - The package is published to NuGet
> >
> > Repeat for each package, at least :
> >
> > - Windows x86
> >
> > - Windows x64
> >
> > And optionally, since .net core is opening the way to .net on
> everything, include the other platforms too.
> >
> > What do you think about it?
>
> Thanks,
> cube45
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> https://mailman.videolan.org/listinfo/vlc-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20170816/1fba96de/attachment.html>