I don't know if I'm overlooking something obvious or if there is a major bug in Visual Web 2005. I have a number of both simple
..html forms and more complex .aspx forms and in attempting to make very simple changes to things like the background color of the
forms, that I used to do through the design view and properties window I find that I can no longer do, because the properties window
seems to have removed many references to the properties of the document. For example, where the background color used to be listed
as a property of the form under the heading "document" I now find only the ability to alter the document's title - there are no
other rows present. There is no longer any place to alter any of the other document properties. The properties window seems to work
fine for all other controls, but not properties realted to the document itself. I once found this and took home the files to work
there, and all was okay on my home machine. Now the problem is occurring on both of my machines. This occurs for both existing forms
and new forms.
Has anyone else run across this issue?
Jeff
--
Posted via a free Usenet account from http://www.teranews.com
..html forms and more complex .aspx forms and in attempting to make very simple changes to things like the background color of the
forms, that I used to do through the design view and properties window I find that I can no longer do, because the properties window
seems to have removed many references to the properties of the document. For example, where the background color used to be listed
as a property of the form under the heading "document" I now find only the ability to alter the document's title - there are no
other rows present. There is no longer any place to alter any of the other document properties. The properties window seems to work
fine for all other controls, but not properties realted to the document itself. I once found this and took home the files to work
there, and all was okay on my home machine. Now the problem is occurring on both of my machines. This occurs for both existing forms
and new forms.
Has anyone else run across this issue?
Jeff
--
Posted via a free Usenet account from http://www.teranews.com