Comments on: Customizing Application Master Pages – part 5 of 6

By: lovemossnot

lovemossnot — Tue, 02 Mar 2010 01:36:08 +0000

Thank you, great post…

ps: SharePoint love baby!!

By: arpug8

arpug8 — Fri, 11 Dec 2009 23:42:32 +0000

I am having the same issues as fengji. The page object comes as null or it doesn't hit the breakpoint at all. I did deploy the assemply to GAC & updated the web.config file too. Is there anything else which I am missing?

By: Ivan Versluis

Ivan Versluis — Mon, 16 Nov 2009 09:46:00 +0000

Very good explanation and post. Unfortunately I was not able to get it working with the shown example of code here.

It took me some time to figure out the GAC copy of DLL to this c:windowsassembly folder. After struggling for two hours I worked through code and server configuration.

My development Sharepoint 2007 is ready and the http module working fine. This is very good solution to solve the application.master issue. My masterpages were so custom that users are confused when uploading or change settings without the correct application.master template.

Thank you for showing me the way to a solution

By: fengji

fengji — Fri, 13 Nov 2009 01:54:05 +0000

this is very good article,

however, when I follow all the instruction and run VS debugging model by attaching to W3WP process, I have the following issues

1. page always return to null from HttpContext.Current.Handler

2. VS doesn't always catch the code hitting when IE is launched

any suggestions will be very appreciated

thanks,

Michael

By: Incorporating a Master Page into a SharePoint site definition | SharePoint Magazine

Fri, 06 Nov 2009 08:45:23 +0000

[...] Customizing the Application.master Page. [...]

By: httprab

httprab — Wed, 04 Nov 2009 16:26:52 +0000

http://rabbitmaomao.spaces.live.com/blog/cns!F9…

By: Brian

Brian — Sun, 23 Aug 2009 13:05:43 +0000

I used your http module concept and it seemed to work great. But now I am noticing an object failing to initialize error when using the people picker. The validate user check throws a javascript error too.

By: ggalipeau

ggalipeau — Thu, 23 Jul 2009 18:19:49 +0000

That is an interesting question Manu. In the reference I gave to the Microsoft “suggestions” on how to customize the application master page (which I do not support), they say that one way is to modify the file in the 12 hive. In my mind, that should void the warranty because you are not suppose to modify 12 hive files.
So, the approach I am suggesting is to avoid doing that. Thus, I believe this is a safter approach to still stay in the guidelines of your SharePoint warranty. Because, you are not modifying anything out of the box, you are leveraging the code to change the master page.
Anyways, I don't know of any official statement from Microsoft about this, but I think this is the safest approach to modify the application master while still staying in the guidelines of how Micorosoft tells us we can customize SharePoint.

By: manu

manu — Tue, 21 Jul 2009 19:08:42 +0000

Hi Greg,
Will such customization void warranty on MOSS?

Regards,
Manu

By: Mike

Mike — Fri, 19 Jun 2009 20:27:29 +0000

I've spent the the past 2 months architecting and preparing for our Moss implementation. To this point, I've relied on a custom theme/css because of this issue alone. This is by far the best solution I've seen for addressing this headache. Thank you for posting this article.