http://msdn2.microsoft.com/library/tsxh3b71.aspx
It seemed to make a lot of sense - x controls in the same container, prevent ID clashes by creating a unique one, but is seems to have been discontinued, or erased... or worse. Is there a standard method of avoiding these clashes without EnsureID?
Following upgrade to 2005 beta 2, code that was previously fine is now producing an error:
Label errorLabel = new Label();
errorLabel.EnsureID();
"-> System.Web.UI.Control.EnsureID() is inaccessible due to its protection level"
Firstly - what is the change, I can't seem to find...
Thanks for the post - yeah probably should have copied the code in a little more carefully, hence the (). TableCell doesn't have a SkinID parameter but WebControl does so no problem there - also the Skin itself applies fine.
What I'm interested in is the "you are setting a SkinID property to a...
c# and ASP.NET
When setting a SkinID which contains a property such as BackColor:
TableCell thisCell = new TableCell;
thisCell.SkinID = "redSkin";
...If I attempt to access the property after this:
Color cellColor = thisCell.BackColor;
...cellColor is null. I'm assuming that either the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.