Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • LibVLCSharp LibVLCSharp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 80
    • Issues 80
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VideoLANVideoLAN
  • LibVLCSharpLibVLCSharp
  • Issues
  • #360
Closed
Open
Issue created Jun 30, 2020 by Martin Finkel@mfklMaintainer

VLC plugin framework for dotnet

Problem to solve

Some dotnet users would like lower access to the VLC core.

Intended users

dotnet libvlcsharp users who want advanced customization.

Proposal

With dotnet 5's official support for native exports, it would be possible in theory to build a VLC plugin in dotnet, that can be loaded and called from the VLC Core. Once that's done, we could provide a framework/bootstrapper nuget that'd allow users to write their own VLC plugin easily.

  • https://wiki.videolan.org/Hacker_Guide/How_To_Write_a_Module/
  • https://wiki.videolan.org/OutOfTreeCompile/

Documentation

Lots I guess.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking

VideoLAN code repository instance