Difference between revisions of "C Sharp"

From VideoLAN Wiki
Jump to navigation Jump to search
(Summarizing tonight's chat on IRC #freenode, with personal additions.)
(Add prominent link to https://code.videolan.org/videolan/LibVLCSharp)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{See also|libVLC Visual C++}}
 +
{{Website|libVLCSharp|on=code.videolan.org|https://code.videolan.org/videolan/LibVLCSharp}}
 
This page refers to all the Work using the .Net platform interaction with VLC.
 
This page refers to all the Work using the .Net platform interaction with VLC.
  
Line 22: Line 24:
 
== License considerations ==
 
== License considerations ==
  
* Using ActiveX API allows any license for your caller code.<ref>[http://www.jbkempf.com/blog/post/2007/09/19/Misconceptions-about-VLC-1-Building-an-application-on-VLC Misconceptions about VLC - 1 Building an application on VLC.]</ref>
+
* Using ActiveX API allows any license for your caller code.
 
* Since LibVLC is LGPL, using it directly allows proprietary code (but watch out respecting LGPL, which includes letting end user replace the LGPL library with their own variant).
 
* Since LibVLC is LGPL, using it directly allows proprietary code (but watch out respecting LGPL, which includes letting end user replace the LGPL library with their own variant).
 
* Some wrappers have a permissive licence (e.g. MIT) which also allows proprietary code.
 
* Some wrappers have a permissive licence (e.g. MIT) which also allows proprietary code.
 
 
==References==
 
{{Reflist}}
 
  
 
[[Category:Bindings]]
 
[[Category:Bindings]]

Latest revision as of 06:36, 20 April 2019

This page refers to all the Work using the .Net platform interaction with VLC.

You can find HowTos and other informations.

Approaches

  • You can incorporate the VideoLAN ActiveX control like any other ActiveX Control (generating an Interop Assembly using `aximp.exe`, etc). In practice this is Windows-only.
  • You can use a .NET wrapper for libVLC (see below). Compatible with more platforms.
  • You can write your own wrapper. Writing a wrapper to LibVlc from .NET should not be that hard. Or adjust an existing wrapper to your liking.

Related projects dealing with a .Net wrapper for libvlc:

Vlc.DotNet is the most advanced as of January 2016.

License considerations

  • Using ActiveX API allows any license for your caller code.
  • Since LibVLC is LGPL, using it directly allows proprietary code (but watch out respecting LGPL, which includes letting end user replace the LGPL library with their own variant).
  • Some wrappers have a permissive licence (e.g. MIT) which also allows proprietary code.