Hi Jan,

The change is from the Paul Wislon MasterPages in 1.1 framework to the official 2.0 .NET MasterPages.
The markup part of your .aspx pages has to be different in 2.0, see one of the other pages to understand.
You no longer need the declarations for those content regions. In 2.0 .NET the declarations are managed automatcially for you in .designer.cs files

old way:

<portal:MasterPage runat="server" id="MPContainer">
    <portal:ContentRegion id="MPTitle" runat="server"></portal:ContentRegion>
    <portal:ContentRegion id="MPLeftPane" runat="server"></portal:ContentRegion>
    <portal:ContentRegion id="MPContent" runat="server" Visible="True">
   
    Your content and controls here
   
    </portal:ContentRegion>
    <portal:ContentRegion id="MPRightPane" runat="server"></portal:ContentRegion>
</portal:MasterPage>

new way:

<asp:Content ContentPlaceHolderID="leftContent" ID="MPLeftPane" runat="server" />
<asp:Content ContentPlaceHolderID="mainContent" ID="MPContent" runat="server">

Your content and controls here

</asp:Content>
<asp:Content ContentPlaceHolderID="rightContent" ID="MPRightPane" runat="server" />
<asp:Content ContentPlaceHolderID="pageEditContent" ID="MPPageEdit" runat="server" />

Hope it helps,

Joe

I don't think so. If you right click them there might be a conversion you can do that will automatically move the declarations and create the .designer.cs file for you. At least I recall that from when I did it. Its not essential to split them into partial classes but that is consistent with how new files will be created.

Joe

Hi Jan,

Yes I didn't mean to imply that markup was all there is to it, but looking at any site page for example, LinksEdit.aspx, look in the  markup and in the code behind for things you might need.

For example your page should inherit from mojoBasePage. I generally set AutoEventWireup=false in the .aspx file and hookup my own events in OnInit but you don't have to do it that way.

You can put content into any of the content regions.

Hope it helps,

Joe

Hi Jan,

when you say table do you mean raw html table or DataGrid or some kind of server controls?
Raw html table should style according to your properties or CSS settings.
Server controls like DataGrid will take their style from the theme.skin file unless you put a setting on it like SkinID="plain". Since there is no skin named "plain" it effectively will disconnect it from the theme.skin file.
Or you can set properties on the theme.skin file in your skin folder to style the server controls.

I'm not sure of a good way to make it use the same theme at design time as it does at runtime. At design time it might be using the App_Themes/Default/theme.skin but at runtime it should use the one in your skin folder.
I hardly ever use the designer so I'm not as up on these things as I should be. If you customize your theme.skin file you might try and copy it into App_themes/Default and see if that makes it look right at design time.

Hope it helps,

Joe