SharePoint Name.dll ActiveX Fix has been Featurized 1

My friend Larry Riemann and I have taken my Name.DLL ActiveX Fix and turned it into a deployable Feature / Solution called SPAXO. The nice thing about SPAXO is that it will apply the fix to all pages on your site no matter what master page is applied without you having to add the Javascript code to your master page manually. We accomplish this by using the .Net HTTPModule to inject the Javascript into the page stream automagically. At this point the code is a major Use At Your Own Risk. If you are feeling daring, head over to Codeplex and give it a shot. CodePlex: SPAXO (SharePoint ActiveX Override)

Update to my SharePoint Name.dll ActiveX Fix

Dave Ginn recently tried out my name.dll fix (read more about it in my previous post) and ran into a problem with some users not being able to access the Site Actions menu. Personally, I have deployed the code to several external MOSS sites and not run into the problem. Let me know in the comments if you have used my fix code successfully or not, as I’m trying to determine what sort of setup causes it to occur. Note: Dave fixed his problem with some code modifications and posted it to his site. I may end up rolling this code back into my source here at this blog.

Fixing the name.dll ActiveX Problem the Mossman Way 5

UPDATE: Are you using SharePoint 2010? See my newer post about the name ActiveX message in SharePoint 2010. Have you seen this message on public facing SharePoint sites: The Web site wants to run the following add-on: ‘Name ActiveX Control’ from ‘Microsoft Corporation’. If you trust the Web site and the add-on and want to allow it to run, click here… For an example of one (at least until they fix it), check out: http://www.viacom.com/pages/default.aspx There are quite a few nice examples of internet facing SharePoint 2007 sites on the interwebs these days, however many of them seem to be plagued by this minor annoyance that seems to have slipped through the Microsoft cracks. The problem is compounded by the fact that most developers won’t even notice the issue until their portal is available to internet users. This is due to the fact that the problem is seen only in Internet Explorer 7 and only ...