Difference between revisions of ".Net Interface to VLC"
| Line 6: | Line 6: | ||
[[IPlayer|IPlayer.cs]] is the main Interface supported by VlcUserControl, since something like this deserves the Bridge pattern treatment. [[IPlayer|IPlayer.cs]] should really be in a different assembly from the control to allow other controls to support it and be used interchange-ably with VlcUserControl but that's up to you developers. | [[IPlayer|IPlayer.cs]] is the main Interface supported by VlcUserControl, since something like this deserves the Bridge pattern treatment. [[IPlayer|IPlayer.cs]] should really be in a different assembly from the control to allow other controls to support it and be used interchange-ably with VlcUserControl but that's up to you developers. | ||
| − | [[ | + | [[NativeLibVlc.cs]] contains the .Net Interop versions of the native VLC C++ structures and functions, and a class which wraps these calls in C#. |
Revision as of 01:08, 1 January 2007
Work from Tappen and Odyssee on the forum.
I started with Odysee's work [1] and wrote a .Net user control that uses libvlc interfaces to do what the ActiveX control does and more, like getting info about and getting/setting audio and subtitle tracks, aspect ratios, deinterlacing filters and more. This compiles in Visual C#.Net Express, free from Microsoft [2].
IPlayer.cs is the main Interface supported by VlcUserControl, since something like this deserves the Bridge pattern treatment. IPlayer.cs should really be in a different assembly from the control to allow other controls to support it and be used interchange-ably with VlcUserControl but that's up to you developers.
NativeLibVlc.cs contains the .Net Interop versions of the native VLC C++ structures and functions, and a class which wraps these calls in C#.
