Exception on BitmapFrame.Create (bug in WPF framework?)
I hope my answer help you,
I had using same code, but BitmapFrame.cs (at PresetationCore.dll) occur Exception when we are using BitmapFrame.Create(source).
So, I just Using other create function below one, which is Inner function of BitmpaFrame.Create,
BitmapFrame.cs
public static BitmapFrame Create(
BitmapSource source,
BitmapSource thumbnail,
BitmapMetadata metadata,
ReadOnlyCollection<colorcontext> colorContexts
)
we can get same result BitmapFrame.Create(source, null, null, null).
- in your case,
enc.Frames.Add(BitmapImage.Create(bitmap, null, null, null));
thanks.
This is by design. A first-chance exception notification doesn't mean that there's a problem. The relevant code inside the Create() method looks like this:
try
{
metadata = source.Metadata as BitmapMetadata;
}
catch (NotSupportedException)
{
}
In other words, the exception is expected and simply swallowed. Which is certainly very annoying since these exceptions do make the debugger stop when you have the Thrown checkbox checked in the Debug + Exception dialog. But it certainly is not a bug, this was intentionally written this way. Sometimes it is a lot cheaper to just let an exception be thrown and swallowing it instead of writing the code that prevents the exception. Especially when it gets unpractical to avoid the exception, the case with bitmaps since there are so many different kind of bitmap types. Some of which don't support metadata. Wherever this is done inside the framework code, it is almost always done to make the code faster. Speed is also an important aspect of code.
Feature, not a bug. Untick the Thrown checkbox to avoid seeing these exceptions.