-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.ArgumentException occurs with Font Family in Win2D Controls on Windows in VS Code #24609
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
This may be a packaged/unpackaged difference. Because Windows apps cannot be launched via the CLI/VSCode :( we use an unpackaged app. VS uses packaged by default. Now, does this help you? Not really, but it will explain why the different IDEs behave differently. What is the value that eventually gets to the font family? |
@mattleibow, Thank you for your details.
There is already an existing issue in WinUI when building the project on the Unpackaged version on Visual Studio: |
Any update on this issue? |
Please provide high priority for this issue. |
Description
When running a .NET MAUI application in Visual Studio Code on Windows, a
System.ArgumentException
with the message "Value does not fall within the expected range" occurs if the font family is set for any Win2D-drawn custom controls. The exception does not occur when running the same project in Visual Studio.Replication sample:
FontFamilyIssue.zip
Steps to Reproduce
Link to public reproduction project repository
No response
Version with bug
8.0.82 SR8.2
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
No response
Did you find any workaround?
No
Relevant log output
No response
The text was updated successfully, but these errors were encountered: