You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exploring the trim warnings from the TrimTest project shows the following areas where having a feature switch(es) could help:
Not to use WPF assemblies (assume UseWPF property is set to false).
Separate design time (where trimming is not required) and runtime experiences. Design time experience should be able to leverage trim incompatible capabilities like reflection and the publishing experience for trimmed applications should not generate trim warnings for the code that is only leveraged only at design time.
The vast majority of the trim warnings are actually not hit by simple WinForms applications like the TrimTest project. However, the following areas are unlikely to be supported in trimming
Trimming WinForms will require a set of feature switches to be used similar to other feature switches when trimming WinForms applications.
Exploring the trim warnings from the TrimTest project shows the following areas where having a feature switch(es) could help:
property
is set to false).System.Drawing.Design.UITypeEditor.IsSupported
System.Windows.Forms.Control.AreDesignTimeFeaturesSupported
System.ComponentModel.DefaultValueAttribute.IsSupported
ComponentModel
in a trim safe way. See the new API proposalSystem.Windows.Forms.Primitives.TypeConverterHelper.UseComponentModelRegisteredTypes
System.Windows.Forms.Primitives
assemblySystem.Windows.Forms.Control.UseComponentModelRegisteredTypes
System.Windows.Forms.ActiveXImpl.IsSupported
System.Windows.Forms.MdiWindowDialog.IsSupported
System.Windows.Forms.ImageIndexConverter.IsSupported
BinaryFormatter
Default_Trimmed_Warnings_wpf_attributes_excluded_ComponentModel_ICustomTypeDescriptor.txt
System.ComponentModel.TypeDescriptor.SupportsInstanceBasedDescriptors
System.ComponentModel.TypeDescriptor.IsComObjectDescriptorSupported
System.ComponentModel.NullableConverter.IsSupported
The text was updated successfully, but these errors were encountered: