How demz20/azuremediaservicesmvc works
Project type and purpose
• This is a full-stack ASP.NET MVC web application that demonstrates end-to-end video upload, encoding, and playback using Azure Media Services.
• Users authenticate via ASP.NET Identity, upload videos through the MVC site, and the app uses Azure Media Services SDK to store, encode, and stream videos.
File structure
• Top-level project “AzureMediaServiceMVC” contains the usual MVC folders:
• Controllers (AccountController, HomeController, ManageController, VideoController)
• Models (AspNetIdentity plus Azure Media Services entities & context)
• Views (Account, Home, Manage, Video + shared layouts)
• Scripts & Content (JS libraries, CSS, jQuery UI themes)
• App_Start (authentication & routing configuration)
• Configuration files (Web.config, BundleConfig, Startup.Auth, MediaServicesCustomPreset.xml)
• There is no separate backend service or microservice—everything lives in one IIS-hosted MVC app.
• External dependency: Azure Media Services (and underlying Blob Storage), plus a local/remote SQL database for Identity.
README for additional insights
• Purpose: upload videos, show upload progress, show encoding jobs, play videos when ready.
• The demo uses Azure Media Encoder presets (MediaServicesCustomPreset.xml) to transcode uploads.