Skip to content
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

[6.0.1] Microsoft.Data.Sqlite: Handle more nulls in ApplicationDataHelper #26637

Merged
merged 1 commit into from
Nov 15, 2021

Conversation

bricelam
Copy link
Contributor

@bricelam bricelam commented Nov 11, 2021

In 6.0, we enabled our UWP code for detecting the temp and data directory to work on the new net5.0-windows (and 6.0) TFMs. For some reason on .NET Core 3.1, this also causes GetType("Windows.Storage.ApplicationData") to return non-null now but GetProperty("LocalFolder") to return null leading to a NullReferenceException.

Fixes #26574

Customer impact

Because this code runs during static initialization of the ADO.NET connection type it is impossible to work around this issue making it impossible to use the 6.0.0 version of Microsoft.Data.Sqlite on .NET Core 3.1 on Windows.

Regression?

Yes, from 5.0.

Risk

Low. The new handling of null results in the same code path that has been used for several releases.

Verification. Manually verified that the library can be used on .NET Core 3.1. Our automated tests only execute on the latest runtime.

@bricelam bricelam requested a review from a team November 11, 2021 19:07
Copy link
Member

@AndriySvyryd AndriySvyryd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please apply patch template

@bricelam bricelam added this to the 6.0.x milestone Nov 12, 2021
@sebastienros
Copy link
Member

NB, AFAIK today is the last day to merge in release/6.0 for next service release

@Shane32
Copy link

Shane32 commented Nov 20, 2021

Our automated tests only execute on the latest runtime.

!?!?!?!? Perhaps Microsoft could afford some automated testing here, at least prior to a major release!

@AndriySvyryd
Copy link
Member

@Shane32 That refers to only tests that run on PRs and during CI. We do have other, more extensive test passes for each release.

@bricelam bricelam deleted the weird branch April 19, 2022 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants