Minimal Repro: MedieElement fails on HTTPS #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
January 11, 2022 22:04
When `MediaElement.Source` is set to a HTTPS-Uri - .NET 4.8 Project throws `NullReferenceException` at System.Windows.Media.MediaPlayerState.OpenMedia(Uri source) at System.Windows.Media.MediaPlayerState.SetSource(Uri source) at System.Windows.Media.MediaPlayerState.Open(Uri source) - .NET Core 5.0 Application sucessfully plays the Source. Plain HTTP works in both runtimes. See https://stackoverflow.com/questions/30702505/playing-media-from-https-site-in-media-element-throwing-null-reference-exception dotnet/wpf#722 fixed and merged with dotnet/wpf#969 into .NET Core.
- Window Icons funktionieren wohl anders, vorübergehend entfernt
eFloh
force-pushed
the
bugs/https-mediaelement-repro
branch
from
004348c to
f8973e6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
MediaElement.Sourceis set to a HTTPS-UriNullReferenceExceptionat System.Windows.Media.MediaPlayerState.OpenMedia(Uri source)
at System.Windows.Media.MediaPlayerState.SetSource(Uri source)
at System.Windows.Media.MediaPlayerState.Open(Uri source)
Plain HTTP works in both runtimes.
See
https://stackoverflow.com/questions/30702505/playing-media-from-https-site-in-media-element-throwing-null-reference-exception
dotnet/wpf#722
fixed and merged with dotnet/wpf#969
into .NET Core.
This PR does not solve the problem, justs proofes the bug and shows a Workaround: Using .NET Core 5.0 Runtime instead of classic .NET Framework App.