I hope your well. That's a great question.
It's certainly possible to swap out the standard InstantForum MasterPage.master with your own custom master page however you should be aware that the InstantForum MasterPage contains a number of controls that will be lost unless you copy these into your master page and set-up via the Page_Load event for your MasterPage.
For example we have checks within our MasterPage Page_Load event to check if the current user is authenticated and display the appropriate options (login or profile).We also set-up some navigation options such as the Explore menu via the MasterPage code-behind so we can apply role based security to the forum list shown within the Explore menu.
You will lose some of this functionality if you completely swap out the InstantForum master page. If you wanted to add controls that appear within the InstantForum MasterPage back into your custom MasterPage you would need to copy these controls from the InstantForum MasterPage.Master into your MasterPage as well as the associated code-behind that sets up the control from the InstantASP.InstantForum.UI/MasterPage.cs file.
The easiest way to use your master page is to simply pop a copy of your "entertainment.master" into the root of the skin folder used for your forum.
You'll need to rename "entertainment.master" to "MasterPage.Master". I'd suggest renaming the existing MasterPage.Master to something like OldMasterPage.Master. This will save you having to go through each .aspx within InstantForum and updating the MasterPage property from "MasterPage.Mater" to "entertainment.master".
If your entertainment.master has any dependencies on compiled DLLs you'll need to ensure these DLLs are copied into the bin folder for the child forum application.
Also if you have a entertainment.master.cs or entertainment.master.vb you'll need to ensure this code-behind is also copied alongside your mater page.
If you prefer not to duplicate your entertainment.master another option may be to add a virtual directory into your forum application within IIS called "shared". This virtual directory would point to the root of your parent application. You could then use...
As your root web site contains a web.config and bin folder you may need to ensure the virtual directory is also marked as a web application within IIS. Once created you can right click the virtual directory and select "Convert to Application" within IIS.
If your looking to simply wrap static HTML around InstantForum and your entertainment.master contains this HTML (with no dynamic server side code you need to preserve) the easiest option may be to simply copy the existing static HTML for your master page into the standard MasterPage.Master file and reference any CSS / JS you need from the MasterPage.Master file. This way you don't need to worry about dependencies or adding virtual directories within IIS etc.
Does this help Mac. I've not had a chance to test these ideas however if they fail please let me know and I'll certainly investigate in more detail.
I look forward to hearing from you and assisting further,
email@example.comBlog | Community