Is it ideal that master page and content will be independent as long as passing information is concerned or it's neccessary that they should pass information in some cases?
Some times you need to pass information between masterpage and your .aspx page (or view page if it is asp.net mvc), but it really depends on what you mean by passing.
The master page can be setup so you can access the HTML title so you can dynamically set the page title. e.g. in a CMS application, you may need to change the html title dynamically based on which article is displayed.
You may also want to set the theme of the site based on the section of the website, so you might require sending back information to the master page to set the appropriate .css file to include.
Note that in many cases you are not really 'sending back' information, rather you are just setting the various content placeholders you created in your master page.
1 answers
Some times you need to pass information between masterpage and your .aspx page (or view page if it is asp.net mvc), but it really depends on what you mean by passing.
The master page can be setup so you can access the HTML title so you can dynamically set the page title. e.g. in a CMS application, you may need to change the html title dynamically based on which article is displayed.
You may also want to set the theme of the site based on the section of the website, so you might require sending back information to the master page to set the appropriate .css file to include.
Note that in many cases you are not really 'sending back' information, rather you are just setting the various content placeholders you created in your master page.
answered 10 months ago by:
400