When working in Asp.net, I discovered something interesting about namespace.\u00a0 Before I explain what that is, a little background…<\/p>\n
If a page accesses it’s masterpage through the typical this.Master way, then any custom methods you’ve written aren’t accessible as it as typed as a MasterPage, not your class that inherits it (presumably something like _MyMasterPage).\u00a0<\/p>\n
You can get around this easily with something like the following:
\n_MyMasterPage _myMaster = this.Master;
\n\/\/now I methods specific to the _MyMasterPage class<\/p>\n
I don’t like repeating that code all over the place, so I usually have a BasePage class that inherits from System.Web.UI.Page and then my pages inherit from it.\u00a0 That way, I can write code like the following: Private void Page_Load(… Public _MyMaster MasterExtensions Since this is a project with no clutter (all data and logic are in other libraries, I thought I’d just put the BasePage class(es) in App_Code.\u00a0<\/p>\n That’s when I hit a problem that rarely comes up.\u00a0 App_Code it’s in the project root namespace.\u00a0 I had set a default root in the project properties of [ClientCompany].[ProjectName].WebUI.\u00a0 And pages could refer to the BasePage class in App_Code, so you would think that App_Code followed that rule, but it doesn’t.\u00a0 It builds another namespace, but makes that namespace an automatic import to the rest of the project.\u00a0<\/p>\n So where’s my problem?\u00a0 I refered to _MyMaster a class that is tied to my specific MasterPage.\u00a0 It’s in the default namespace.\u00a0 And App_Code doesn’t get an automatic reference back to project namespace.<\/p>\n Solution: Go into the Base class page and give it a: Another way to solve this (that I’m probably going to do), is to put an interface to the MasterPage in App_Code.\u00a0 It’s cleaner anyway, in case you end up with multiple masters.<\/p>\n","protected":false},"excerpt":{"rendered":" When working in Asp.net, I discovered something interesting about namespace.\u00a0 Before I explain what that is, a little background… If a page accesses it’s masterpage through the typical this.Master way, then any custom methods you’ve written aren’t accessible as it as typed as a MasterPage, not your class that inherits it (presumably something like _MyMasterPage).\u00a0 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23,34,18,24],"tags":[],"class_list":["post-62","post","type-post","status-publish","format-standard","hentry","category-aspnet","category-microsoft","category-programming","category-web"],"_links":{"self":[{"href":"http:\/\/hoolihan.net\/blog-tim\/wp-json\/wp\/v2\/posts\/62","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/hoolihan.net\/blog-tim\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/hoolihan.net\/blog-tim\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/hoolihan.net\/blog-tim\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/hoolihan.net\/blog-tim\/wp-json\/wp\/v2\/comments?post=62"}],"version-history":[{"count":0,"href":"http:\/\/hoolihan.net\/blog-tim\/wp-json\/wp\/v2\/posts\/62\/revisions"}],"wp:attachment":[{"href":"http:\/\/hoolihan.net\/blog-tim\/wp-json\/wp\/v2\/media?parent=62"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/hoolihan.net\/blog-tim\/wp-json\/wp\/v2\/categories?post=62"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/hoolihan.net\/blog-tim\/wp-json\/wp\/v2\/tags?post=62"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nPublic class BasePage
\n_MyMasterPage _master;<\/code><\/p>\n
\n{
\n_master = this.Master;
\n}<\/p>\n
\n{
\n\/\/get…
\n}
\n<\/code>
\nNow, each page (that inherits off of BasePage)\u00a0can call MasterExtensions.Whatever() without any setup.\u00a0 And base page can hold similar methods that it’s handy for all pages to be able to call.\u00a0<\/p>\n
\nusing [ClientCompany].[ProjectName].WebUI;<\/code>
\nMost of the time, this doesn’t come up because classes in App_Code are fairly generic and not tied back to the UI classes.<\/p>\n