Was asked to post this into this thread from the MSDN forums;
thread here.
I've tested the following problem on multiple development computers, which includes as an additional test a fresh VM with Windows XP and Visual Studio 2008 as well as VS 2008 SP1. The problem is non-existant on a fresh install of VS 2008 but once I apply SP1, the problem shows it's ugly face.
The issue is when I have a web control that has one or more expandable properties and the web control is contained within another web control, such as a Panel, the expandable properties of the child control do not properly persist to the Source view window. During my tests, I am using Split view to view the changes made to the control in the designer as well as reviewing whether to properties are persisting.
Screenshots:
Image may be NSFW.
Clik here to view.
Image #1: Shows a web control (GridView) not contained within a container web control. The expandable property AlternatingRowStyle contains the CssClass property that I changed the value from the default empty string to the string "Test" and it property persisted to the Source view as <AlternatingRowStyle CssClass="Test" />.
Image may be NSFW.
Clik here to view.
Image #2: Shows the same web control (GridView) now inside another web control (Panel) with the same property changed, but to a different value for emphasis that it is different than the previous screenshot. Note that the tab with the name of the file at the top of the screenshot doesn't show an asterisk (*) even though I changed the value of the property from it's default value (empty string) to "AnotherTest" and pressed enter.
I've tested this with several other controls with expandable properties, and every test has come out the same, so it's not just the Style typed properties. Although, I have noticed that the FontInfo properties do not have this same "feature". When I change one of the font properties on the controls, they do persist to the source view, regardless of whether there is a parent control.
