結論:可以
驗證demo如下:
using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms; namespace IconTest { public partial class Form2 : Form { public Form2() { InitializeComponent(); ReflectTest rt = new ReflectTest(); rt.GetType().GetProperty("ID").SetValue(rt, "Guid", null); MessageBox.Show(rt.ID); } } public class ReflectTest { private string id; [ReadOnly(true)] public string ID { get { return id; } set { id = value; } } } }
運行winform小註:
TypeDescriptor.GetProperties(rt)["ID"].SetValue(rt, "Guid");那為什麼TypeDescriptor.GetProperties用來setvalue沒有效果呢?
將上面的程式碼拆成如下兩句:
PropertyDescriptor prop = TypeDescriptor.GetProperties(rt)["ID"]; prop.SetValue(rt, "Guid");
單點追蹤進去,可以發現: or這個抽象類別的實例後,在呼叫SetValue方法的時候,是從其子類別ReflectPropertyDescriptor呼叫的。
而具體的實作是在子類
public override void SetValue(object component, object value) { #if DEBUG if (PropDescUsageSwitch.TraceVerbose) { string compName = "(null)"; string valName = "(null)"; if (component != null) compName = component.ToString(); if (value != null) valName = value.ToString(); Debug.WriteLine("[" + Name + "]: SetValue(" + compName + ", " + valName + ")"); } #endif if (component != null) { ISite site = GetSite(component); IComponentChangeService changeService = null; object oldValue = null; object invokee = GetInvocationTarget(componentClass, component); Debug.Assert(!IsReadOnly, "SetValue attempted on read-only property [" + Name + "]"); if (!IsReadOnly) { // Announce that we are about to change this component // if (site != null) { changeService = (IComponentChangeService)site.GetService(typeof(IComponentChangeService)); Debug.Assert(!CompModSwitches.CommonDesignerServices.Enabled || changeService != null, "IComponentChangeService not found"); } // Make sure that it is ok to send the onchange events // if (changeService != null) { oldValue = SecurityUtils.MethodInfoInvoke(GetMethodValue, invokee, (object[])null); try { changeService.OnComponentChanging(component, this); } catch (CheckoutException coEx) { if (coEx == CheckoutException.Canceled) { return; } throw coEx; } } try { try { SecurityUtils.MethodInfoInvoke(SetMethodValue, invokee, new object[] { value }); OnValueChanged(invokee, EventArgs.Empty); } catch (Exception t) { // Give ourselves a chance to unwind properly before rethrowing the exception. // value = oldValue; // If there was a problem setting the controls property then we get: // ArgumentException (from properties set method) // ==> Becomes inner exception of TargetInvocationException // ==> caught here if (t is TargetInvocationException && t.InnerException != null) { // Propagate the original exception up throw t.InnerException; } else { throw t; } } } finally { // Now notify the change service that the change was successful. // if (changeService != null) { changeService.OnComponentChanged(component, this, oldValue, value); } } } } }
從程式碼可以看出來,只讀屬性直接被跳過去了。 。 。 。 。 。
那麼PropertyInfo有沒有什麼限制呢?
PropertyInfo調用的SetValue如下圖所示:
SetValue有什麼限制
PropertyInfo.GetSetMethod可以利用反射來賦值唯讀屬性嗎?的內容,更多相關內容請關注PHP中文網(www.php.cn)!