We have been experimenting with MOSS 2007 as a CMS for our organization. As an educational organization subject to 508 compliance, our front end web designers/developers have specfied that we need to get the CSSAdapters implemented on the Shareponint navigation controls so they can go nuts with CSS.
We found this article http://blogs.tamtam.nl/frank/ , so, myself and one other person here in our organization have been struggling with getting it to work on a regular asp.net menu control, but using an assembly instead of the .VB source code files (we can get it to work with .vb code files to work without issue).
So, here is what we have done that does work well…
Dowloaded and installed the CSS Friendly ASP.NET 2.0 Control Adapters code from MS.
As discussed in the article, we created a new web app using the , and, added a class library which included all the adapter code files and we compiled to a signed assembly named: CSSAdapters.dll.
We registered the assembly to the GAC, and, can verify that it exists (c:\windows\assembly\cssAdapters)
Here’s where we ran into trouble…
We moved the CssAdapter.browser file, into C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\Browsers and edited it to look for our assembly in the GAC:
<adapter controlType="System.Web.UI.WebControls.Menu"
adapterType="CSSFriendly.MenuAdapter, CssAdapters,
version=1.0.0.0,
Culture=neutral,
PublicKeyToken=<The Token>"/>
We attempted to register the adapter at the machine level by running aspnet_regbrowsers.exe but got a “Cannot Load Type CSSFriendly.MenuAdapter” error.
As you can imagine, we’ve done all kinds of testing and we’ve verified…
We can use CSSAdapters.DLL when placed in the BIN of a local test site in combination with the local .browser file configured like this:
<adapter controlType="System.Web.UI.WebControls.Menu"
adapterType="CSSAdapters.CSSFriendly.MenuAdapter, CssAdapters"/>
So, this tells us that the .dll is good, and, all the associated code is good (right?).
We think our error is getting ASP.NET to play nice with the machine level so when we try to move all this over to the MOSS 2007 it will pick it up. I don’t think that is possible if we try to just drop the App_Code and App_Browser files over into the root dir of the MOSS installation (right?).
I think if we can get the support of the ASP.NET community in working through this problem, this could be a huge help to others that come along later.
Thanks for any assistance you can offer.
Bernie