
The RadPageLayout still has problems in design mode, In fact, the message appears: "Error Rendering Control. An unhandled exception has occurred. Request is not available in this context" .
This problem prevents us from seeing the contents within the control and prevents change in design mode the control properties.
I hope this problem will be solved as soon as possible because it greatly penalizing !!!
Thanks in advance
29 Answers, 1 is accepted
We are aware for this problem and will try to fix it for the upcoming service pack. When the issue is resolved we will notify you.
Please excuse us for any inconveniences caused.
Regards,
Peter Filipov
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

It would be useful to be able to change even in design mode the RadPageLayout control settings, so as to shorten the time of the creation of the user interface.
This will be the next of the design. For the SP1 we will try to fix the error and show the nested controls.
Regards,
Peter Filipov
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.


Is there a release date for sp1? We are really looking forward to move on using radpagelayout.
tx
Sven
I am writing to inform you that the problem is resolved and the fix is available in the internal builds. Keep in mind that we are using PlaceHolders controls to keep our content and the nested controls are to accessible in design time. Even though you could access their smart tags in the source view of the aspx page.
@Sven you could use the control it is fully functional in Q2.2014. The design time issue shouldn't be a stopper for you. In case that you have question please open a support ticket and we will assist you further.
Regards,
Peter Filipov
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

Thanks for solving that problem.
Now the error does not give it more, but it is still the problem that you can not see the controls inside the content in a master page.
I work with all content pages that use a master page and the controls are not yet seen.
Now if I want to work in design mode, I am forced to use a master page without radpagelayout, then once finished construction, resubmit the original master page.
I look forward to further developments.
This is the expected behavior of the PlaceHolder, in case that you place it in a content page and put your controls inside you will get the same result. In case that you want to access the smart tag you should click on the control definition and hover the prefix and the smart tag will appear.
Regards,
Peter Filipov
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

I'm a little bit confused now.
Could you provide a sample using masterpage?
thanks
Sven

I also have the problem with RadPageLayout in design mode (the new release is just installed). A sample would be very helpful.
Thanks,
Susanne
Currently, there is no designer for RadPageLayout, but we do plan to bring one for a later release.
Unlike other controls, which deal mostly with data, RadPageLayout deals with layouts and we really want to think and plan the designer carefully.
Regards,
Ivan Zhekov
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

It is still the problem that you can not see the controls inside the content in a master page.
I work with all content pages that use a master page and the controls are not yet seen.
Look with confidence to be corrected sooner or later !!
Thanks

I'm quite interested in hearing about this too. Even when not using master/content pages, I have serious design-view issues.
Eg. the RadRibbonView rendering wrong and unable to select child controls.
It is a great idea, but it doesn't really seem mature yet.
For the time being RadPageLayout remains to be without a proper (or any) support for design view. The main problem with it is the intricate rendering composition it has and the latter has proven challenging to implement for design time.
Regards,
Ivan Zhekov
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.


This is an issue which is related with the PlaceHolders elements that we are using. In case that you need to access the smart tag this could you be done through the source code page by hovering the prefix (VS 2013). Until now we have no other solution to overcome that problem otherwise we are going to introduce a breaking change.
Regards,
Peter Filipov
Telerik

We understand that this is a problem for the users and we are going to make a deeper research how this behavior could be changed.
Regards,
Peter Filipov
Telerik

OK, here we are in Feb 2016 we still have NOTHING for design view, how do you expect that anyone can really use this control?
I was hoping this would allow a new critical project to be Telerik based across the board, but apparently not.
You REALLY REALLY need to fix this.


How in design mode it is not usable.
The library Telerik.Web.Device.Detection.Detector.GetScreenSize not work !!!
When these things will be put right?
We haven't found any proper solution to this problem to suites the developers and our business needs. It is an option to use the smart tag of the controls inside the PageLayout by clicking on the telerik definition in the source view.
Regarding to the issue with the device detection, could you please be more specific and send us detailed explanation of the problem that you are experiencing.
Regards,
Peter Filipov
Telerik

Page Layout forces you to work in code-mode all of the time. There are times when design mode saves me time with naming controls , finding things easier, etc... With the page layout in design mode you can't do anything but look at a bunch of garbage and you can see any controls. Maybe that is tied to ASP.Net master pages in my case.
Device detection could be enhanced if for say I am using the Chrome developer tool and emulating an iPhone 6 it could recognize that. However it only (seems) to know the computer monitor resolution I am developing in so it is always detecting the largest resolution.
Robert
We understand this but is a limitation of the asp.net webforms, because we are using placeholders controls, in case that you put a components inside the PlaceHolder control you will get the same behavior.
Regarding to the Device Detection Framework, we are going to update it in the next releases to include data from more devices.
Regards,
Peter Filipov
Telerik

Any progress with the design view issue?
Using VS 2015 and Telerik 2016.3.1303.45
Still cannot use design view.
Thanks,
~bg

I completely changed the project moving to Bootstrap and I finally solved the problem.
I could not wait until the problems were resolved.

Any word on this? I am getting this error:
Error Creating Control - RadPageLayout1Failed to create designer 'Telerik.Web.UI.RadPageLayout, Telerik.Web.UI, Version=2016.3.914.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4'
Can you please check the following blog post and article on the topic:
Best regards,
Rumen
Telerik by Progress