R – Master Page location of controls in content page

asp.netmaster-pages

I'm trying to rebuild a site using masterpages. I copied the markup of the controls in the old page and placed them in the content place holder in the new page(in source view).

Since they were absolutely positioned the controls do not stay inside the content place holder in design view. Everything is between the content place holder tags in source view.

the page works when I run it. Is there anything wrong in leaving it like this? I can't seem to drag all the controls into the content placeholder in design view.

Best Answer

Honestly I very rarely use the design view. It is much easier and faster to just type it out by hand and by doing so you become more accustomed to the language. As for old content you can just paste it into the source and it should work fine barring mistakes in the old content of course. The Design View is not always going to accurately display your code so I would not worry too much about. You should try to build the page and make sure there are not any small discrepancies though.

Related Solutions

R – Convert Web Form to Web Content Form after the fact. (.net)

For each page do the following - Add an attribute to the <@Page > tag named MasterPageFile="Your MasterPage Path" - Add the following tag - Remove html and head tags and their contents except body tag - Remove the body tags BUT KEEP its contetnts - Remove the form tag - Done

R – How to provide easy editing of ASP .NET master pages for designers

Would it be possible for you to put placeholders in the Master Page in place of the areas that designers should be allowed to edit? Since Master Pages are only editable in Visual Studio, it may be your only feasible option at this point in time. One problem with this approach is that the content put in the placeholders is unlikely to be valid, since you would probably have tags left open in one placeholder and closed in another.

<html>
<head>
<title></title>
<asp:PlaceHolder ID="headerContent" runat="server"></asp:PlaceHolder>
</head>
<body>

<asp:PlaceHolder ID="beforeContent" runat="server"></asp:PlaceHolder>

<asp:PlaceHolder ID="centralContent" runat="server"></asp:PlaceHolder>

<asp:PlaceHolder ID="afterContent" runat="server"></asp:PlaceHolder>

</body>
</html>

I know it's ugly, but it might give you the control you need (as long as you don't mind the XHTML validator warning you all the time). What you put in the placeholders could be your user controls or literal content or whatever, but you'd have to load it dynamically.

Thoughts?

EDIT: This won't work. The PlaceHolder is going to render <div> tags that would mess things up. Maybe you could extend PlaceHolder and override how it renders its HTML.

Best Answer

Related Solutions

R – Convert Web Form to Web Content Form after the fact. (.net)

R – How to provide easy editing of ASP .NET master pages for designers

Related Topic