Aren't master pages meant to inherit from umbraco.presentation.masterpages._default?
It looks like that has some code which enables LiveEditing support. Pretty sure if you don't want to try LiveEditing then you don't need to inherit from that though.
Hmm I didn't know that existed, yes if you're after live editing support you could inherit it if you're not inheriting from the umbraco standard masterpage.
Remember that masterpages can be nested, so your masterpage doesn't need an umbraco type if you're nesting under a masterpage which does.
I only knew it because when you create a Template via the Umbraco interface it creates a blank .master file which inherits from that. What do you mean by the umbraco standard masterpage? I thought this was it.
IMHO nested master pages are the best way to work with umbraco (prior to MVC at least) - I got my main template wrapper in a single .master file and all the pages on the site are children of that.
What intellisense are you missing? If its to do with not being able to access public things in the master master then try putting this into your child master page:
Is there Umbraco classes for Page, MasterPage or User Controls that I should inherit from ?
Is there Umbraco classes for Page, MasterPage or User Controls that I should inherit from ?
Or just System.Web.UI.Page ?
No, there are no custom classes. You should just use the standard ASP.NET ones
Thanks.
Aren't master pages meant to inherit from umbraco.presentation.masterpages._default?
It looks like that has some code which enables LiveEditing support. Pretty sure if you don't want to try LiveEditing then you don't need to inherit from that though.
Hmm I didn't know that existed, yes if you're after live editing support you could inherit it if you're not inheriting from the umbraco standard masterpage.
Remember that masterpages can be nested, so your masterpage doesn't need an umbraco type if you're nesting under a masterpage which does.
I only knew it because when you create a Template via the Umbraco interface it creates a blank .master file which inherits from that. What do you mean by the umbraco standard masterpage? I thought this was it.
And I've never notice it set a class define when i create one.
Oops my bad mine says that too..... it's THAT default.master than inherits from umbraco.presentation.masterpages._default
Correct. Id' always recommend that you have your root-most masterpage have that as its parent unless you plan to reimplement the Umbraco class
So I also found these:
umbraco.presentation.masterpages.umbracoPage
umbraco.presentation.masterpages.umbracoDialog
umbraco.presentation.masterpages._default
By the way, nested master pages really sucks because it breaks the intellisense in Visual Studio and it's seems wrong...
IMHO nested master pages are the best way to work with umbraco (prior to MVC at least) - I got my main template wrapper in a single .master file and all the pages on the site are children of that.
What intellisense are you missing? If its to do with not being able to access public things in the master master then try putting this into your child master page:
Then you can do Master.Label1 or whatever and it will intellisense it up for you.
I'm missing all the asp: tags... in master pages that inherit from the default master,
(when I open it with with visual studio)
so it does. wonder why that is....
Because you are not supposed to nest master pages... inheritance is fine though...
course you are supposed to nest them.... it's a feature
http://msdn.microsoft.com/en-us/library/x2b3ktt7.aspx
Yes, you are right, I just found the same page :-)
But still can't figure out why Visual Studio wont recognize asp: tags
is working on a reply...