Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

What is the recommended approach for resolving these two warnings?#4210

Unanswered
NeverMorewd asked this question inQ&A
Discussion options

[IL2026] Using member 'ReactiveUI.IReactiveNotifyPropertyChanged<TSender>.SuppressChangeNotifications()' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. SuppressChangeNotifications uses extension methods that may require unreferenced code.
[IL2026] Using member 'ReactiveUI.ReactiveObject.SuppressChangeNotifications()' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. This method uses reflection to access properties by name.
You must be logged in to vote

Replies: 1 comment 1 reply

Comment options

I am also searching for an answer to that question. This is related to#4018
As far as I know, there is no possibility to suppress specific warnings coming from an referenced package.

@glennawatson , do you know a way to suppress these warnings without

  1. having to add 1.000+ annotations to the own methods which leads to a pretty ugly codebase
  2. suppressing the warnings globally for the entire project/codebase (which would also hide real issue warnings)
You must be logged in to vote
1 reply
@glennawatson
Comment options

Unfortunately Microsoft hasn't really given a way to suppress warnings from a particular library as far as I'm aware.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
3 participants
@NeverMorewd@glennawatson@dabbinavo
[8]ページ先頭
©2009-2025 Movatter.jp