London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
ContentFrameworkSelector
You should implement MasterPages with ContentPlaceHolders instead, introduced in .NET Framework 2.0.
#23007
Aug 23, 2008 17:56
Hi,
I am upgrading a site from .NET 1.1 and Visual Studio 2003 to .NET 2.0 and Visual Studio 2005.
My problem is that EPiServer:ContentFrameworkSelector does not work after my upgrade.
How can I write the following code to make it work in .NET 2.0 and when I upgrade to EPiServer CMS 5?
Code:
<EPiServer:ContentFrameworkSelector Runat="server" FrameworkKeyName="MyMode" ID="FrameworkSelector" DefaultFramework="DefaultFramework">
<Ulh:DefaultFramework ID="DefaultFramework" Runat="server">
<EPiServer:Content Region="FullBoxRegion" Runat="server">
<Ulh:Resource Runat="Server" />
</EPiServer:Content>
</Ulh:DefaultFramework>
<Ulh:DefaultFramework ID="CalendarView" Runat="server">
<EPiServer:Content Region="FullBoxRegion" Runat="server">
<Ulh:ResourceCalendar Runat="Server" />
</EPiServer:Content>
</Ulh:DefaultFramework>
</EPiServer:ContentFrameworkSelector>
Thanks!
/Frida S